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

JAVA_HOME env variable not populating path to JDK installation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: javanet-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2008 R2
      Ubuntu 12.04 LTS
    • Similar Issues:

      Description

      When performing a build on a Maven project, the build gets the following error:

      ERROR: Failed to parse POMs
      java.io.IOException: Cannot run program "/bin/java" (in directory "E:\Program Files\Jenkins\jobs\GAFRI ESB\workspace"): CreateProcess error=2, The system cannot find the file specified

      We have JAVA_HOME set as a system environment variable and it used to configured the path to the JDK installation. This worked until recently. The environment variable is no longer being populated for Maven project.

        Attachments

          Activity

          Hide
          sodul Stephane Odul added a comment -

          I'm getting this quite often on maven builds but not consistently. Eventually the Slave will gets its brain back together and get the jvm that it auto install, but it cause a bit of confusion and complaints from our developers.

          Show
          sodul Stephane Odul added a comment - I'm getting this quite often on maven builds but not consistently. Eventually the Slave will gets its brain back together and get the jvm that it auto install, but it cause a bit of confusion and complaints from our developers.
          Hide
          sodul Stephane Odul added a comment -

          Getting this issue fairly consistently now every time we restart the master with Jenkins 1.559 on Ubuntu 12.04 LTS. It clears itself up eventually but this is very distracting every time we restart the master and generates dozen of 'broken' builds.

          Show
          sodul Stephane Odul added a comment - Getting this issue fairly consistently now every time we restart the master with Jenkins 1.559 on Ubuntu 12.04 LTS. It clears itself up eventually but this is very distracting every time we restart the master and generates dozen of 'broken' builds.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cjaehnen Chris Jaehnen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: