[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title Alex Earl closed an issue as Cannot Reproduce No response on whether this occurs on more recent versions of Jenkins Jenkins / JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses Change By: Alex Earl Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title A B commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses Sorry. I understood your idea. In config.xml it should berh http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz jdk1.8.0_111 Now it works perfectly. Thank you so much Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title A B commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses Thanx for quick response. Unfortunately the result is the same. In config.xml I have: rh http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz 111 In console output I have: Building remotely on 006(qualif) (qualif006 xvfb rh) in workspace /usr/local/jenslavessh/slave_root/workspace/test006-java Unpacking http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz to /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 on 006(qualif) [test006-java] $ /bin/sh -xe /tmp/hudson4829290230800605707.sh + echo PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin + echo JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111 JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111 + java -version java version "1.7.0_101" OpenJDK Runtime Environment (rhel-2.6.6.4.el6_8-x86_64 u101-b00) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) + /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin/java -version /tmp/hudson4829290230800605707.sh: line 5: /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/111/bin/java: No such file or directory Build step 'Execute shell' marked build as failure Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title Daniel Beck commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses A B Different issue, and in your case it's misconfiguration: Set the Subdirectory of extracted archive configuration option. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title A B edited a comment on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses I have this problem with Jenkins 2.2, and redhat6 slave.In my case I use 'Extract *.tar.gz' installer.The file jdk- 8u45 8u111 -linux-x64.tar.gz (retrieved from Oracle manually) is successfully downloaded and unpacked.When starting the job using this installer I have JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk- 8u45 8u111 -linux-x64However, it is installed in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk- 8u45 8u111 -linux-x64/jdk1.8. 0_45 0_111 Thus, the last part of the path (jdk1.8. 0_45 0_111 ) is lost.The détails:In config.xml I have: jdk- 8u45 8u111 -linux-x64rh http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk- 8u45 8u111 -linux-x64.tar.gz .In job config.xml I have: jdk- 8u45 8u111 -linux-x64In console output I have:Building remotely on 006(qualif) (qualif006 xvfb rh) in workspace /usr/local/jenslavessh/slave_root/workspace/test006-javaUnpacking http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz to /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 on 006(qualif)[test006-java] $ /bin/sh -xe /tmp/hudson6955254772848194612.sh+ echo PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/binPATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin+ echo JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64+ java -versionjava version "1.7.0_101"OpenJDK Runtime Environment (rhel-2.6.6.4.el6_8-x86_64 u101-b00)OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)+ /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java -version/tmp/hudson6955254772848194612.sh: line 5: /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java: No such file or directoryBuild step 'Execute shell' marked build as failureFinished: FAILUREAnd java is located in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/jdk1.8.0_111/bin/java Add Comment
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title A B edited a comment on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses I have this problem with Jenkins 2.2, and redhat6 slave.In my case I use 'Extract *.tar.gz' installer.The file jdk-8u45-linux-x64.tar.gz (retrieved from Oracle manually) is successfully downloaded and unpacked.When starting the job using this installer I have JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk- 8u111 8u45 -linux-x64However, it is installed in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk- 8u111 8u45 -linux-x64/jdk1.8. 0_111 0_45 Thus, the last part of the path (jdk1.8. 0_111 0_45 ) is lost.The détails:In config.xml I have: jdk-8u45-linux-x64rh http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u45-linux-x64.tar.gz .In job config.xml I have: jdk-8u45-linux-x64In console output I have:Building remotely on 006(qualif) (qualif006 xvfb rh) in workspace /usr/local/jenslavessh/slave_root/workspace/test006-javaUnpacking http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz to /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 on 006(qualif)[test006-java] $ /bin/sh -xe /tmp/hudson6955254772848194612.sh+ echo PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/binPATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin+ echo JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64+ java -versionjava version "1.7.0_101"OpenJDK Runtime Environment (rhel-2.6.6.4.el6_8-x86_64 u101-b00)OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)+ /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java -version/tmp/hudson6955254772848194612.sh: line 5: /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java: No such file or directoryBuild step 'Execute shell' marked build as failureFinished: FAILUREAnd java is located in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/jdk1.8.0_111/bin/java Add Comment
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title A B commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses I have this problem with Jenkins 2.2, and redhat6 slave. In my case I use 'Extract *.tar.gz' installer. The file jdk-8u45-linux-x64.tar.gz (retrieved from Oracle manually) is successfully downloaded and unpacked. When starting the job using this installer I have JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 However, it is installed in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/jdk1.8.0_111 Thus, the last part of the path (jdk1.8.0_111) is lost. The détails: In config.xml I have: jdk-8u45-linux-x64 rh http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u45-linux-x64.tar.gz . In job config.xml I have: jdk-8u45-linux-x64 In console output I have: Building remotely on 006(qualif) (qualif006 xvfb rh) in workspace /usr/local/jenslavessh/slave_root/workspace/test006-java Unpacking http://jenkins-tools-master.ivs.lab.ingenico.com/java-packages/jdk-8u111-linux-x64.tar.gz to /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 on 006(qualif) [test006-java] $ /bin/sh -xe /tmp/hudson6955254772848194612.sh + echo PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin PATH = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin + echo JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 JAVA_HOME = /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64 + java -version java version "1.7.0_101" OpenJDK Runtime Environment (rhel-2.6.6.4.el6_8-x86_64 u101-b00) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) + /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java -version /tmp/hudson6955254772848194612.sh: line 5: /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/bin/java: No such file or directory Build step 'Execute shell' marked build as failure Finished: FAILURE And java is located in /usr/local/jenslavessh/slave_root/tools/hudson.model.JDK/jdk-8u111-linux-x64/jdk1.8.0_111/bin/java Add Comment
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov commented on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses Ok, I have finally managed to cleanup the old config paths - these were in the registry at various locations, such as: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6.0_31 ... What you need to do is search in all keys/values/data for the JDK signature, e.g., "1.6.0_31", also search the wrong JDK paths, e.g., "hudson" in this case. Then all remote installations from the master of JDKs will proceed in the proper places. I guess the headless installer that forces 'yes' on all questions, also uses any default suggestions that the installer may make for directories, and an existing one happens to override the instructed place to install argh! 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
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java'jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java\jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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 Qassar commented on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses 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. The JDK files do not appear in this directory. 4) Going up a directory, a directory has appeared in C:\jenkins\tools\1.6.0_30. Inside it are a jre directory, applets.zip, demos.zip, src.zip, and tools.zip (the components of the JDK installation). It seems that the installer is putting the output of the install in the wrong place and not unpacking the JDK. 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. 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 Qassar edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses 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. The JDK files do not appear in this directory. 4) Going up a directory, a directory has appeared in C:\jenkins\tools\1.6.0_30. Inside it are a jre directory, applets.zip, demos.zip, src.zip, and tools.zip (the components of the JDK installation). It seems that the installer is putting the output of the install in the wrong place and not unpacking the JDK. 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. 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
candrews created JENKINS-13864: -- Summary: JDK auto installer installs to a different path than JAVA_HOME for a build uses Key: JENKINS-13864 URL: https://issues.jenkins-ci.org/browse/JENKINS-13864 Project: Jenkins Issue Type: Bug Components: infrastructure, slave-setup Affects Versions: current Reporter: candrews Assignee: Kohsuke Kawaguchi Priority: Blocker I have a Linux Jenkins server, and a Windows slave (I haven't tested yet to see if this is an issue with non-Windows slaves). In the settings page, I have configured Jenkins to auto install Java SE Development Kit 7u3 from java.sun.com When I launch a build which uses Java, Jenkins downloads and install the JDK onto the slave, but then, when the build is run, JAVA_HOME is not set to the directory that the JDK was installed to. In the build output, here is what I see when the JDK is installed: Installing c:\jenkins\tools\JDK\Java_7\jdk.exe [Java_7] $ c:\jenkins\tools\JDK\Java_7\jdk.exe /s /v /qn /L \c:\jenkins\tools\JDK\Java_7\jdk.exe.install.log\ REBOOT=ReallySuppress INSTALLDIR=\c:\jenkins\tools\JDK\Java_7\ During the build, JAVA_HOME is set to c:\jenkins\tools\JDK\Java_7\ However, the JDK is actually installed to C:\jenkins\tools\Java_7 So it appears that the c:\jenkins\tools\JDK\Java_7\jdk.exe installer is installing to C:\jenkins\tools\Java_7 but, according to its command line invocation's INSTALLDIR parameter, and to what Jenkins sets as JAVA_HOME, it should be installing to c:\jenkins\tools\JDK\Java_7\ This problem starts with Jenkins version 1.464. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
