[
https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160542#comment-160542
]
Alex Gray commented on JENKINS-13136:
-------------------------------------
Unfortunately no.
In the first project (this is the "virgin" project with nothing checked) I see
the PATH variable containing stuff from Jenkins master). JAVA_HOME env is
fine.
The second project (where I am using the EnvInjec to inject "foo=bar" I see the
PATH variable being tweaked the same as the first project, but it also
incorrectly contains JAVA_HOME pointing to Jenkins master.
I did a diff between the injectEnvVars.txt (which are in the zip file that I
provided too), and they are indeed different. The moment I use the EnvInject
to simply inject "foo=bar", I get every single env var from Jenkins Master. I
think that is the root cause.
Its kinda weird that for virgin projects (not using any plugins) the PATH
variable is being tweaked from stuff on the master.
If you want I can upgrade from 1.35 to 1.38 (again) and re-run this experiment.
Thanks for looking into this!
> 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
> Attachments: EnvInjectData.zip
>
>
> 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
