Allow replacing remoting version being shipped to agents without core update

XMLWordPrintable

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: 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

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

              Created:
              Updated: