Spin-off of JENKINS-16490. In Jenkins project we use this library for managing Windows Agents/Slaves. It's being done by launching a slave.jar via Java. Since the remoting library (effectively slave.jar) is being updated frequently, we would like to have an option to download it from the Jenkins instance directly.
For such purpose I propose to implement a WinSW plugin
winsw/winsw#126
Originally reported by
oleg_nenashev, imported from: Add option to update slave.jar in Windows Service Wrapper on startup (when Jenkins runs on HTTPS)
- assignee:
oleg_nenashev
- status: Resolved
- priority: Major
- component(s): remoting, windows-slave-installer-module
- label(s): 2.46.3-rejected, remoting, winsw
- resolution: Fixed
- resolved: 2017-03-13T16:05:55+00:00
- votes: 6
- watchers: 9
- imported: 2025-11-25
Raw content of original issue
Spin-off of JENKINS-16490. In Jenkins project we use this library for managing Windows Agents/Slaves. It's being done by launching a slave.jar via Java. Since the remoting library (effectively slave.jar) is being updated frequently, we would like to have an option to download it from the Jenkins instance directly.
For such purpose I propose to implement a WinSW plugin
winsw/winsw#126
Spin-off of
JENKINS-16490. In Jenkins project we use this library for managing Windows Agents/Slaves. It's being done by launching a slave.jar via Java. Since the remoting library (effectively slave.jar) is being updated frequently, we would like to have an option to download it from the Jenkins instance directly.For such purpose I propose to implement a WinSW plugin
winsw/winsw#126
Originally reported by
oleg_nenashev, imported from: Add option to update slave.jar in Windows Service Wrapper on startup (when Jenkins runs on HTTPS)
Raw content of original issue