[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured

[ho...@se-rwth.de (JIRA)]

Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured These are excerpts from some build console outputs. With config.no.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T16:52:50.204 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 60423 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... With config.with.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T17:14:44.362 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/bin/java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 43246 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_65, vendor: Oracle Corporation Java home: /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... As you can see, the first build is IMHO run with the wrong JDK since the default JDK there is the OS JDK and NOT the single JDK known to Jenkins (which was 1.7.0_u65). Only after selecting the right JDK in the job configuration (which required adding a second JDK installation) the build was executed with the right JDK (second console output).

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

--
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.