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

Hidden dependencies to WMI windows agents + uninstallation does not work

    • 82.v692fff78926d clone scm workspace plugin and 27.vb_9404db_b_018d of email-ext-recipients-column-plugin

      At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

      After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

       

      My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

      I guess it might be a good idea to:

      • mark the culprit(s) with an explicit dependency
      • mark the culprit(s) deprecated as well

      Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

       

      JFTR: uninstallation of windows-slaves-plugin did not work. The warning and the plugin came back after each try.

      Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation) does not work. It's back after a restart.

          [JENKINS-70148] Hidden dependencies to WMI windows agents + uninstallation does not work

          Christoph Fetzer created issue -
          Christoph Fetzer made changes -
          Component/s New: windows-slaves-plugin [ 18327 ]
          Christoph Fetzer made changes -
          Description Original: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.
          New: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          It only worked "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation.
          Christoph Fetzer made changes -
          Description Original: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          It only worked "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation.
          New: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation does not work. It's back after a restart.
          Christoph Fetzer made changes -
          Description Original: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation does not work. It's back after a restart.
          New: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation) does not work. It's back after a restart.
          Christoph Fetzer made changes -
          Summary Original: Hidden dependencies to WMI windows agents New: Hidden dependencies to WMI windows agents + uninstallation does not work
          Christoph Fetzer made changes -
          Description Original: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warninging and the plugin came back after each try.

          Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation) does not work. It's back after a restart.
          New: At my jenkins installation (2.361.4) the WMI windows agents plugin appeared deprecated.

          After disabling it, I was not able to start any jobs. So I enabled it again and started removing the marked implicitly dependent plugins I do not work with and disabled WMI windows agents again.

           

          My finding: either extended emails recipient columns plugin or clone workspace SCM plugin (or both) must have a real dependency.

          I guess it might be a good idea to:
           * mark the culprit(s) with an explicit dependency
           * mark the culprit(s) deprecated as well

          Otherwise it will cause some trouble as soon as WMI windows agents plugin will be removed in the future.

           

          JFTR: uninstallation of windows-slaves-plugin did not work. The warning and the plugin came back after each try.

          Even using "the hard way" (deleting both the jip file and the plugin folder in the plugins folder of the installation) does not work. It's back after a restart.
          Mark Waite made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Mark Waite made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Mark Waite made changes -
          Released As New: 82.v692fff78926d clone scm workspace plugin

            Unassigned Unassigned
            chrisfetz Christoph Fetzer
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: