[JIRA] (JENKINS-12963) EnvInject plugin causes job to use JAVA_HOME instead of configured JDK
[ https://issues.jenkins-ci.org/browse/JENKINS-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159775#comment-159775 ] SCM/JIRA link daemon commented on JENKINS-12963: Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter.java http://jenkins-ci.org/commit/envinject-plugin/b4ea67db856dea01458351b9addc5a6c30bc3c7b Log: Fix JENKINS-12963 > EnvInject plugin causes job to use JAVA_HOME instead of configured JDK > -- > > Key: JENKINS-12963 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12963 > Project: Jenkins > Issue Type: Bug > Components: envinject >Reporter: jvoegele >Assignee: gbois >Priority: Critical > > After upgrading the EnvInject plugin from version 1.17 to 1.30, Jenkins jobs > stopped using the JDK configured for the job and would instead use the JDK > referred to by the JAVA_HOME environment variable. For example, a test job > that was configured for JDK 1.5 would run with JDK 1.6.0_30, as shown by the > following console output: > JAVA_HOME=/X/hotspot1.6.0_30 > ... > Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_30 > Java home: /X/hotspot1.6.0_30/jre > The jobs are "free-style software projects" which use Maven in some of the > build steps. > Downgrading the plugin to the previously installed 1.17 version fixed this > problem, but I do not know exactly what version introduced the issue. -- 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
[JIRA] (JENKINS-12963) EnvInject plugin causes job to use JAVA_HOME instead of configured JDK
[ https://issues.jenkins-ci.org/browse/JENKINS-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12963. - Resolution: Fixed > EnvInject plugin causes job to use JAVA_HOME instead of configured JDK > -- > > Key: JENKINS-12963 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12963 > Project: Jenkins > Issue Type: Bug > Components: envinject >Reporter: jvoegele >Assignee: gbois >Priority: Critical > > After upgrading the EnvInject plugin from version 1.17 to 1.30, Jenkins jobs > stopped using the JDK configured for the job and would instead use the JDK > referred to by the JAVA_HOME environment variable. For example, a test job > that was configured for JDK 1.5 would run with JDK 1.6.0_30, as shown by the > following console output: > JAVA_HOME=/X/hotspot1.6.0_30 > ... > Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_30 > Java home: /X/hotspot1.6.0_30/jre > The jobs are "free-style software projects" which use Maven in some of the > build steps. > Downgrading the plugin to the previously installed 1.17 version fixed this > problem, but I do not know exactly what version introduced the issue. -- 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
[JIRA] (JENKINS-12963) EnvInject plugin causes job to use JAVA_HOME instead of configured JDK
jvoegele created JENKINS-12963: -- Summary: EnvInject plugin causes job to use JAVA_HOME instead of configured JDK Key: JENKINS-12963 URL: https://issues.jenkins-ci.org/browse/JENKINS-12963 Project: Jenkins Issue Type: Bug Components: envinject Reporter: jvoegele Assignee: gbois Priority: Critical After upgrading the EnvInject plugin from version 1.17 to 1.30, Jenkins jobs stopped using the JDK configured for the job and would instead use the JDK referred to by the JAVA_HOME environment variable. For example, a test job that was configured for JDK 1.5 would run with JDK 1.6.0_30, as shown by the following console output: JAVA_HOME=/X/hotspot1.6.0_30 ... Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) Java version: 1.6.0_30 Java home: /X/hotspot1.6.0_30/jre The jobs are "free-style software projects" which use Maven in some of the build steps. Downgrading the plugin to the previously installed 1.17 version fixed this problem, but I do not know exactly what version introduced the issue. -- 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
