As described in JENKINS-9679, merely updating the version of slave.jar served from Jenkins master does not cause JNLP agents to use the new version; they persist in using the JNLP cache. This makes debugging changes difficult, and can result in bug fixes seeming to not take effect in user deployments.
We do set an immediate Expires header on /jnlpJars/slave.jar but apparently this does not suffice.
- is blocking
-
JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
-
- Closed
-
- is duplicated by
-
JENKINS-21642 JNLP slaves should refresh old slave.jar when possible
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-23880 JNLP slave : slave.jar should update itself when Jenkins is updated
-
- Resolved
-
- is related to
-
-
- Resolved
-
- relates to
-
-
- Closed
-