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

EnvInject plugin causes job to use JAVA_HOME instead of configured JDK

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: envinject-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: