|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14006) EnvInject stop... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)
- [JIRA] (JENKINS-14006) EnvInject... [email protected] (JIRA)

This showed up for me with 1.53 and using the build step for environment injection.
If for a node, you configure the environment (http://localhost:8080/configure Global Properties) by adding a key-value pair such as
PATH => $PATH:/my/custom/tools/path
MY_PROP => Hello World
The modified PATH property will not be set for any build steps executed after a "inject environment properties" step, instead you'll just get the system default that the build slave was started with. However setting properties directly such as MY_PROP continue to work as expected.
To test:
jenkins 1.471
Only additional plugin = EnvInject plugin 1.53
A simple job with build steps (linux)
<shell>
set
echo "HELLO = world" > envionment.properties
</shell>
<Inject environment variables>
Properties file path => envionment.properties
</Inject environment variables
<shell>
set
</shell>
When you run the job, in the console the properties list for the first build step will show the PATH being modified, while after the injection step, you will see the unmodified path.
With an upgrade Environment Injector Plugin v1.55 to the problem occurs for the first build step as well.