[ 
https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160438#comment-160438
 ] 

gbois commented on JENKINS-13136:
---------------------------------

Could you attach your job configuration file (config.xml)?
                
> Environment Variable Injection injecting (and overriding) unwanted variables 
> (ie JAVA_HOME)
> -------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13136
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13136
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>    Affects Versions: current
>         Environment: Jenkins Master: 1.432, hosted on a centos5.3, 32-bit
> Slave Node: Windows XP
> EnvInject: 1.38
>            Reporter: Alex Gray
>            Assignee: gbois
>
> We were using EnvInject 1.35 in various free-style jobs, but after we 
> upgraded to 1.36 jobs started failing.
> This is the reason:
> 1) On the slave node (in this case, a windows XP slave node) JAVA_HOME is 
> pointing to version 1.25.  I can verify this by going to Jenkins->Manage 
> Jenkins->Manage Nodes->MyWinXPNode->"view log", and sure enough the node's 
> environment variables have JAVA_HOME pointing to 1.25
> 2) After upgraded to EnvInject 1.36, the jobs started failing because 
> JAVA_HOME has been overwritten to 1.27, which does not exist on the node.  In 
> fact, I don't know where this is being set because the master does not have 
> java 1.27 either!
> The only option that is is present in the job is this:
> Inject environment variables to the build process
> Properties Content:
>     TEMP=c:\\windows\\temp
>     TMP=c:\\windows\\temp
> (everything else under "Inject Environment Variables" is blank.
> I have not tried the latest version, 1.38, but I will, since all the jobs are 
> currently broken and I have nothing else to lose...
> If it doesn't fix it, then the workaround is to go to EnvInject 1.35, but 
> that does not work on multiconfiguration jobs.
> I'll keep you posted.  If this is fixed in 1.38, I will update this Jira.

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

        

Reply via email to