-
Bug
-
Resolution: Duplicate
-
Major
-
None
If you disable a plugin which has a hard dependency with another plugin, Jenkins doesn't report anything or suggest you to disable/delete the dependencies. At the end, you can end up with stacktraces like:
WARNING: Failed to scout com.cloudbees.opscenter.client.plugin.ClusterSessionClientExtensionHandler java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/plugins/openid/OpenIdExtension at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:354) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.size(ExtensionList.java:162) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:559) at
Jenkins should not allow you to disable a plugin when there is such kind of dependency. It should instead maybe give you also the tree of dependencies so you can uninstall all of them if you want.
A Warning can be also an option saying that it is not possible to remove/disable because there is a dependency with another plugin. I don't like too much this option because you end up with a lot of manual work.
- duplicates
-
JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated
- Resolved
-
JENKINS-21485 AdministrativeMonitor for plugins that have failed
- Resolved
-
JENKINS-23150 Warn users about invalid plugin configurations
- Resolved