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

Allow replacing remoting version being shipped to agents without core update

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      Currently Jenkins always ships Remoting version from the core to agents. Sometimes it would be better to ship newer version (e.g. with a bugfix for agent side, but it requires)

      Proposed changes:

      • API in the Core, which allows replacing Slave.JarFile
      • Plugin, which bundles Remoting as a resource and replaces the resource if the bundled version is newer than the version in the core

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            -1 on this. JENKINS-41196 is better and more general.

            Show
            jglick Jesse Glick added a comment - -1 on this.  JENKINS-41196 is better and more general.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            This is not a competitor of JENKINS-41196, especially since there is no ETA. I have no plans to alter the core logic, I plan to ship only service logic for agent. E.g. somebody will be able to provide custom remoting.jar after the plugin.

            Show
            oleg_nenashev Oleg Nenashev added a comment - This is not a competitor of JENKINS-41196 , especially since there is no ETA. I have no plans to alter the core logic, I plan to ship only service logic for agent. E.g. somebody will be able to provide custom remoting.jar after the plugin.
            Hide
            jglick Jesse Glick added a comment -

            Right, I get that, but why we would have a one-off feature for doing that when JENKINS-41196 is already written and probably just needs some testing and polish?

            Show
            jglick Jesse Glick added a comment - Right, I get that, but why we would have a one-off feature for doing that when  JENKINS-41196  is already written and probably just needs some testing and polish?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Maybe. It depends on the path we select.

            Show
            oleg_nenashev Oleg Nenashev added a comment - Maybe. It depends on the path we select.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            https://github.com/jenkinsci/jenkins/pull/2875 offers code for that. Somebody is welcome to pick it up and reimplement if needed.

            All my use-cases are addressed by https://github.com/jenkinsci/custom-war-packager which allows replacing libraries in WAR bundles.

            Show
            oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/2875 offers code for that. Somebody is welcome to pick it up and reimplement if needed. All my use-cases are addressed by https://github.com/jenkinsci/custom-war-packager which allows replacing libraries in WAR bundles.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: