-
Bug
-
Resolution: Unresolved
-
Major
-
Windows 2008/JDK1.5/1.4.10
Under node configuration, advanced launch options, JVM options are not copied to the jenkins-slave.xml file after executing install windows service function. We can work around this issue by manually editing the jenkins-slave.xml file.
- is duplicated by
-
JENKINS-9908 JNLP slave JVM options are ignored
-
- Resolved
-
-
JENKINS-9909 JNLP slave JVM options are ignored
-
- Resolved
-
-
JENKINS-9910 JNLP slave JVM options are ignored
-
- Resolved
-
- is related to
-
JENKINS-2452 Cannot install slave agent as Windows service
-
- Resolved
-
-
JENKINS-16061 Make jenkins-slave.xml manageable in Windows Agents Plugin
-
- Closed
-
- links to
(1 links to)
For me this also happens if the launch method is "Let Jenkins control this Windows slave as a Windows service."
Jenkins should use the JDK/JRE path to java.exe already installed on the slave system if present, if it did it would also fix
JENKINS-6957for me (system couldn't find java.exe without manually hacking jenkins-slave.xml or adding C:\Windows\SysWOW64 to PATH).