Status: Open (View Workflow)
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)
- 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
- relates to
JENKINS-41196 Pluggable core component
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.
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?
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.
-1 on this.
JENKINS-41196is better and more general.