![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
03/Apr/15 6:23 PM
|
|
Description:
|
A slave's environment variables seem to be cached upon first connect and then never considered again. This prevents legitimate changes to a slave's environment from having any effect on builds. The only workaround I can find is to delete a slave and recreate it, which in a complex environment is unacceptable.
This may be a consequence of JENKINS-26755.
|
|
Environment:
|
Jenkins 1.606
|
|
Project:
|
Jenkins
|
|
Labels:
|
envinronment-variables
slaves
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Milo Hyson
|
|
|
|
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.
