Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: New Feature
Resolution: Won't Do
Priority: Major
Component/s: core, remoting
Labels:

Epic Link:
Remoting Upgradeability

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

JENKINS-22454 When a slave is installed as a service, it should auto-update slave.jar

Resolved

JENKINS-23880 JNLP slave : slave.jar should update itself when Jenkins is updated

Resolved

is related to

JENKINS-39237 Add option to update slave.jar in Windows Service Wrapper on startup (when Jenkins runs on HTTPS)

Resolved

relates to

JENKINS-51820 Remove Java Web Start UI and logic from core

Closed

(1 relates to)

Assignee:: Unassigned
Reporter:: Jesse Glick

Created:: 2013-01-25 17:04
Updated:: 1 hour ago
Resolved:: 2023-05-08 11:30
Archived:: 1 hour ago

Details

Description

Attachments

Issue Links

Activity

People

Dates