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

Windows Slaves plugin should use API of the Windows Agent Installer Module

      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

          [JENKINS-42743] Windows Slaves plugin should use API of the Windows Agent Installer Module

          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 for JENKINS-42743

          SCM/JIRA link daemon added a comment - 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 for JENKINS-42743

          Mark Waite added a comment -

          Won't be fixed. See JENKINS-67604 for the details of the deprecation of agents started by WMI calls using DCOM.

          Mark Waite added a comment - Won't be fixed. See JENKINS-67604 for the details of the deprecation of agents started by WMI calls using DCOM.

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

              Created:
              Updated:
              Resolved: