[
https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161434#comment-161434
]
Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------
Here is the ouput of the job running today with EnvInject 1.36
12:38:15 + cp /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt .
12:38:15 [EnvInject] - Injecting environment variables from a build step.
12:38:15 [EnvInject] - Injecting as environment variables the properties file
path 'BuildFingerprint.txt'
12:38:15 [EnvInject] - Variables injected successfully.
12:38:15 [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
12:38:15 [EnvInject] - Unset unresolved 'PATH' variable.
12:38:15 [EnvInject] - Unset unresolved 'NEWSCP' variable.
12:38:15 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
12:38:15 [EnvInject] - Unset unresolved 'TEMP' variable.
And the content of /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt
[BuildInfo]
BuildId=2012-04-10_12-37-30
BuildNumber=20
DBBuildNumber=4775
BuildName=7.0_RC_Continuous-20
SymbolStoreUUID=92113861832b11e1b3bf00219b99e084
HGRev=c65e9f8e929175f8706a8a51bfecdb10da78503c
Branch=prerelease-7.0-RC
The config is the same that I already have attached.
As I said, the Master Jenkins is running on Windows and the slave on Linux, I
don't know if that changes anything.
I can do more testing by creating a job that only injects the variables, if you
want.
Thanks
> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
> Key: JENKINS-13325
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
> Environment: Jenkins 1.457, Windows master, Linux slave
> Reporter: Marc Sanfacon
> Assignee: gbois
> Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the
> following behavior:
> 08:51:39 [EnvInject] - Injecting environment variables from a build step.
> 08:51:39 [EnvInject] - Injecting as environment variables the properties
> file path 'BuildFingerprint.txt'
> 08:51:39 [EnvInject] - Variables injected successfully.
> 08:51:39 [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39 [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39 [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39 [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a
> script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16 [EnvInject] - Injecting environment variables from a build step.
> 08:49:16 [EnvInject] - Injecting as environment variables the properties
> file path 'BuildFingerprint.txt'
> 08:49:16 [EnvInject] - Variables injected successfully.
> 08:49:16 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails
> when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed
> it.
> Also, why does EnvInject undefines other variables? All I want is for it to
> inject the variables I asked. The ini files does not contain PYTHONPATH.
--
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
