-
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