|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Looks like the problem might have occurred around v1.606. For each of the tests I conducted the following procedure:
1) Started with the following environment variables on the slave machine
PATH = /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
SOME_ENVVAR = value
2) Launched java -jar jenkins.war on the master machine
3) Added a new node to the master
4) Started slave.jar on the slave
5) Ensured PATH and SOME_ENVVAR showed up on master
6) Killed slave.jar
7) Appended :/nonexistent to PATH
8) Removed SOME_ENVVAR
9) Ensured variables changed on slave machine
10) Restarted slave.jar
11) Refreshed node's system-information page on master
The following were the results:
v1.599 without EnvInject
PATH updated on master
SOME_ENVVAR disappeared from master
v1.599 with EnvInject
PATH updated on master
SOME_ENVVAR disappeared from master
v1.606 with EnvInject
PATH did not update on master
SOME_ENVVAR remained on master