Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12963

EnvInject plugin causes job to use JAVA_HOME instead of configured JDK

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • envinject-plugin
    • None

      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=/XXXXX/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: /XXXXX/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.

          [JENKINS-12963] EnvInject plugin causes job to use JAVA_HOME instead of configured JDK

          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

          SCM/JIRA link daemon added a comment - 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

            gbois Gregory Boissinot
            jvoegele jvoegele
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: