Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16490

New versions of Remoting should be automatically pushed to Java Web Start agents

      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.

          [JENKINS-16490] New versions of Remoting should be automatically pushed to Java Web Start agents

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-9679 [ JENKINS-9679 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-21642 [ JENKINS-21642 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-22454 [ JENKINS-22454 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147312 ] New: JNJira + In-Review [ 176870 ]
          Patrick Wolf made changes -
          Assignee New: CloudBees Inc. [ cloudbees ]
          Oleg Nenashev made changes -
          Component/s New: remoting [ 15489 ]
          Oleg Nenashev made changes -
          Assignee Original: CloudBees Inc. [ cloudbees ] New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Labels Original: jnlp slave New: jnlp slave winsw
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-39237 [ JENKINS-39237 ]
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-38833 [ 175240 ]

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            16 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated:
              Resolved: