-
Bug
-
Resolution: Fixed
-
Major
-
Hudson 1.342 on Windows XP Master w/ Windows XP Slaves
When installing a new JDK on a windows slave, there appears to be a quoting issue with the arguments passed to the installer. From the console output:
[jdk-1.6.0_17] $ C:\hudson-tmp\tools\jdk-1.6.0_17\jdk.exe /s '/v/qn REBOOT=Suppress INSTALLDIR=\"C:\hudson-tmp\tools\jdk-1.6.0_17\" /L \"C:\hudson-tmp\tools\jdk-1.6.0_17\jdk.exe.install.log\"'
Notice how the /s is outside of the single quotes where the rest of the options are (/v/qn ...). Comments in the WINDOWS case of JDKInstaller.java#install seem to indicate that the options to the installer should be passed as one string. However, the code adds two strings - one for /s and another for the rest of the options.
The result is that the jdk fails to install. However, executing C:\hudson-tmp\tools\jdk-1.6.0_17\jdk.exe /s /v/qn REBOOT=Suppress INSTALLDIR=\"C:\hudson-tmp\tools\jdk-1.6.0_17\" /L \"C:\hudson-tmp\tools\jdk-1.6.0_17\jdk.exe.install.log\" on a command prompt successfully installs the JDK.
- is duplicated by
-
JENKINS-15945 Auto-install of JDK fails on Windows Slave
-
- Resolved
-
- is related to
-
JENKINS-23366 jdk8u5 installation fails on windows agents
-
- Open
-
-
JENKINS-16733 msiexec hangs due to wrong command line syntax
-
- Resolved
-
Glad to see that this has been fixed. What needs to be done to get the fix into the next LTS version? Our Jenkins build farm runs both Linux and Windows slaves, and this problem forces us to manually install and configure OS-specific JDK versions on all slaves.
Thanks.