The following installed plugins are deprecated: WMI Windows Agents Plugin

[christop...@googlemail.com]

Hi,

I have what we call a "hen-egg-problem" to solve a deprecation warning in latest LTS:

Jenkins warns about deprecation of the WMI Windows agent plugin

When I want to disable that plugin for a test I get a warning, it might be unsafe to disable the plugin because other plugins might depend on it.

And indeed, when it is disabled I can't start any jobs through the UI.

Is there any way to get out of this situation? Otherwise that deprecation warning does not make much sense to me.

Thank!

Christoph

[Mark Waite]

Hover over the "uninstall button" for the WMI Windows Agents plugin in the Jenkins plugin manager and a pop-up will appear that lists the installed plugins that have an implied dependency on the plugin.  Those plugins need to be removed or they need to be adopted and upgraded so that their minimum Jenkins version is a recent Jenkins version.

An implied dependency on the WMI Windows Agents plugin is described in the "What's this?" page that pops up from the "Implied" section of the WMI Agents Plugin dependencies page.

It says:

> Features are sometimes detached (or split off) from Jenkins core and moved into a plugin. Many plugins, like Subversion or JUnit, started as features of Jenkins core.

> Plugins that depend on a Jenkins core version before such a plugin was detached from core may or may not actually use any of its features. To ensure that plugins don't break whenever functionality they depend on is detached from Jenkins core, it is considered to have a dependency on the detached plugin if it declares a dependency on a version of Jenkins core before the split. Since that dependency to the detached plugin is not explicitly specified, it is implied.

> Plugins that don't regularly update which Jenkins core version they depend on will accumulate implied dependencies over time

The last statement is what is happening.  One or more of the installed plugins can be run on a Jenkins core version before WMI Windows Agents plugin was split from Jenkins core.  Those plugins need to either be removed or upgraded.  See the list of plugins in the "Implied" section of the dependencies page for WMI Windows Agents plugin.  If one or more of those installed plugins is critical to you, you can adopt the plugin and use the "Improve a Plugin" tutorial to upgrade the minimum required Jenkins version of the plugin.

Mark Waite

[christop...@googlemail.com]

Hi Mark,

Hm, amongst these plugins are things like ViewVC (not working with CVS currently but I'd try to fix it - was searching on CVS side), email ext recipients column, doxygen, metrics disc usage.

And the fact that I have trouble when disabling WMI window agents tells me there must be a real dependency somewhere, not only implied ones.

Alright, I'll try to disable the plugins I am not working with and disable WMI windows agents again.

Please correct me if I missed something.

Thanks,

Christoph

[christop...@googlemail.com]

But - wait a second. As soon as I found out one or more culprits depending on WMI windows agents these should immediately be declared deprecated, right?

And you can declare the dependency.

Otherwise you'll run in trouble when there are still active installations and WMI won't be shipped any longer.

I'll file issues when I know more...

BR,

Christoph

[Mark Waite]

On Wednesday, November 23, 2022 at 6:46:44 AM UTC-7 Christoph wrote:

But - wait a second. As soon as I found out one or more culprits depending on WMI windows agents these should immediately be declared deprecated, right?

And you can declare the dependency.

Otherwise you'll run in trouble when there are still active installations and WMI won't be shipped any longer.

As far as I can tell from a search of the 1800+ plugins that I have cloned locally, I find only 1 plugin with an explicit dependency on the WMI Windows Agents plugin.  That plugin is  Multi-slave config plugin - last released 8 years ago.

If that plugin is installed, it will need to be removed.

[Daniel Beck]

On Wed, Nov 23, 2022 at 2:26 PM 'christop...@googlemail.com' via Jenkins Users <jenkins...@googlegroups.com> wrote:

And the fact that I have trouble when disabling WMI window agents tells me there must be a real dependency somewhere, not only implied ones.

I'd expect there to be exceptions logged or other (somewhat) visible impact that tells you more. 

[christop...@googlemail.com]

After removing email ext recipients column, Clone Workspace SCM Plug-in and WMI windows agent plugins the warning disappeared and I still can start jobs. One of those two must be really depending on WMI windows agents, I guess.

Thanks for the support!

Christoph

[christop...@googlemail.com]

FYI: JENKINS-70148

[christop...@googlemail.com]

Another observation: uninstallation using the plugin manager did not work. I had to manually remove the jpi and installation folder.

[christop...@googlemail.com]

Sorry - too fast - it's even worse: it comes back by itself after manual uninstallation.