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

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

XMLWordPrintable

      slave.jar should update itself when Jenkins is updated. I have a large qty of remote build agents, and when we see problems, we never know if the outdated slave.jar is relevant or not. This should be changed once and for all so that it detects the change and auto updates itself when the Jenkins server is updated.

      Competing CI servers have had this as basic functionality for years, it would be great if Jenkins supported the same.

            Assignee:
            Unassigned
            Reporter:
            boris ivan
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: