|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
jerry.qas...@kratosdefense.com (JIRA) Thu, 05 Jul 2012 17:41:39 -0700
- [JIRA] (JENKINS-13864) JDK auto inst... candr...@integralblue.com (JIRA)
- [JIRA] (JENKINS-13864) JDK auto... jerry.qas...@kratosdefense.com (JIRA)
- [JIRA] (JENKINS-13864) JDK auto... jerry.qas...@kratosdefense.com (JIRA)
- [JIRA] (JENKINS-13864) JDK auto... diak...@gmail.com (JIRA)
- [JIRA] (JENKINS-13864) JDK auto... diak...@gmail.com (JIRA)
- [JIRA] (JENKINS-13864) JDK auto... diak...@gmail.com (JIRA)
Can corroborate this issue is occurring on recent versions of Jenkins (1.470).
Having a similar issue on a Solaris master (that auto-installs JDKs) with a Windows 7 slave. The output in question for a Maven 3 job is:
Installing c:\jenkins\tools\JDK\jdk-1.6.0_30\jdk.exe
[jdk-1.6.0_30] $ c:\jenkins\tools\JDK\jdk-1.6.0_30\jdk.exe /s /v /qn /L \"c:\jenkins\tools\JDK\jdk-1.6.0_30\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\jenkins\tools\JDK\jdk-1.6.0_30\"
...
[job-trunk] $ c:\jenkins\tools\JDK\jdk-1.6.0_30/bin/java -cp c:\jenkins\maven3-agent.jar;c:\jenkins\tools\Maven\maven-3.0.3\boot\plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main c:\jenkins\tools\Maven\maven-3.0.3 C:\jenkins\slave.jar c:\jenkins\maven3-interceptor.jar 55981
ERROR: Failed to parse POMs
java.io.IOException: Cannot run program "c:\jenkins\tools\JDK\jdk-1.6.0_30/bin/java" (in directory "c:\jenkins\workspace\job-trunk"): CreateProcess error=2, The system cannot find the file specified
When I examine the directories in question:
1) C:\jenkins\tools\JDK\jdk-1.6.0_30 is created and jdk.exe downloads into it.
2) Once complete, the install kicks off (supposedly) and jdk.exe.install.log appears.
3) After a minute, the jdk.exe and log disappear, replaced with an .installedByHudson file.
4) Going up a directory, a directory has appeared in C:\jenkins\tools\1.6.0_30.
Manual Workaround:
Manually install a 6u30 JDK into C:\jenkins\tools\JDK\jdk-1.6.0_30. Not ideal. :/
Attention to the autoinstaller (or the params passed to the installers being downloaded) would be a big help.