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 Mark Waite schrieb am Mittwoch, 23. November 2022 um 13:59:37 UTC+1: > 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 > <https://plugins.jenkins.io/windows-slaves/#dependencies>. > > 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 > <https://plugins.jenkins.io/windows-slaves/#dependencies>. If one or > more of those installed plugins is critical to you, you can adopt the > plugin > <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> > and use the "Improve a Plugin" tutorial > <https://www.jenkins.io/doc/developer/tutorial-improve/update-base-jenkins-version/> > > to upgrade the minimum required Jenkins version of the plugin. > > Mark Waite > On Wednesday, November 23, 2022 at 1:16:53 AM UTC-7 > [email protected] wrote: > >> 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 >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/71314548-6b50-4992-b3fb-2fd744439457n%40googlegroups.com.
