-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.606
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.
- is duplicated by
-
JENKINS-27928 environment variable changes are not applied.
-
- Resolved
-
-
JENKINS-28278 Environment variables "stuck" on windows slave
-
- Resolved
-
- relates to
-
JENKINS-69821 Changes to "built-in" environment variables are ignored always
-
- Open
-
- links to
[JENKINS-27739] Changes to slave environment variables are ignored by master
Link |
New:
This issue is duplicated by |
Assignee | New: Daniel Beck [ danielbeck ] |
Labels | Original: envinronment-variables slaves | New: envinronment-variables lts-candidate slaves |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR 1728 (Web Link)" [ 12928 ] |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: envinronment-variables lts-candidate slaves | New: 1.609.2-fixed envinronment-variables slaves |
Labels | Original: 1.609.2-fixed envinronment-variables slaves | New: 1.609.2-fixed envinronment-variables lts-candidate slaves |
Labels | Original: 1.609.2-fixed envinronment-variables lts-candidate slaves | New: 1.609.2-fixed envinronment-variables slaves |