-
Improvement
-
Resolution: Won't Do
-
Major
Windows Agent Installer Module has been decoupled from the Jenkins core in 1.492: https://github.com/jenkinsci/jenkins/commit/aaf1bf29e630ad251efc21b962987d8d2be32f6d
Windows Slaves plugin depends on the 1.492 core and hence it is expected to use the module's APIs instead of copy-pasting that API implementations and depending on the core components. Usage of new API will enable features like Remoting upgradeability and Runaway process killer, which are available in the new core versions.
It is a follow-up to JENKINS-42724
- is blocked by
-
JENKINS-42745 WindowsSlaveInstaller#generateXml() produces invalid XML in 1.7
-
- Resolved
-
- is related to
-
JENKINS-42724 Windows Slaves Plugin: agent is not starting after upgrade to Jenkins 2.50
-
- Closed
-
-
JENKINS-42746 Windows Slaves Plugin should use internal jenkins-slave.xml
-
- Closed
-
[JENKINS-42743] Windows Slaves plugin should use API of the Windows Agent Installer Module
Summary | Original: Windows Slaves plugin should use API of the Windows Agent Installer <odule | New: Windows Slaves plugin should use API of the Windows Agent Installer Module |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Oleg Nenashev [ oleg_nenashev ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Description |
Original:
Windows Agent Installer Module has been decoupled from the Jenkins core in 1.492: https://github.com/jenkinsci/jenkins/commit/aaf1bf29e630ad251efc21b962987d8d2be32f6d Windows Slaves plugin depends on the 1.492 core and hence it is expected to use the module's APIs instead of copy-pasting that API implementations and depending on the core components |
New:
Windows Agent Installer Module has been decoupled from the Jenkins core in 1.492: https://github.com/jenkinsci/jenkins/commit/aaf1bf29e630ad251efc21b962987d8d2be32f6d Windows Slaves plugin depends on the 1.492 core and hence it is expected to use the module's APIs instead of copy-pasting that API implementations and depending on the core components. It is a follow-up to |
Link |
New:
This issue is related to |
Link |
New:
This issue is blocked by |
Link |
New:
This issue is related to |
Description |
Original:
Windows Agent Installer Module has been decoupled from the Jenkins core in 1.492: https://github.com/jenkinsci/jenkins/commit/aaf1bf29e630ad251efc21b962987d8d2be32f6d Windows Slaves plugin depends on the 1.492 core and hence it is expected to use the module's APIs instead of copy-pasting that API implementations and depending on the core components. It is a follow-up to |
New:
Windows Agent Installer Module has been decoupled from the Jenkins core in 1.492: [https://github.com/jenkinsci/jenkins/commit/aaf1bf29e630ad251efc21b962987d8d2be32f6d] Windows Slaves plugin depends on the 1.492 core and hence it is expected to use the module's APIs instead of copy-pasting that API implementations and depending on the core components. Usage of new API will enable features like Remoting upgradeability and Runaway process killer, which are available in the new core versions. It is a follow-up to - |
Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java
http://jenkins-ci.org/commit/windows-slaves-plugin/63fc71dd1207cda5a6d3884fa304f9bee82de2be
Log:
JENKINS-42746- Amend the TODO comment forJENKINS-42743