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

Allow replacing remoting version being shipped to agents without core update

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None

      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

          [JENKINS-44101] Allow replacing remoting version being shipped to agents without core update

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-44099 [ 181725 ]
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-41196 [ JENKINS-41196 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]

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

              Created:
              Updated: