Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

[Jochen Hayek]

Hi there!

I am experiencing the same problem as described by philm88 here:

http://echelog.com/logs/browse/jenkins/1444600800

In my case no restoring of a backup is involved, and I don't think that particular issue is related.

In the installed plugins page, the enabled box is ticked, but greyed out. Hovering over them says "This plugin cannot be enabled. It has one more disabled dependencies <list>" Of those dependencies listed, they're greyed out unticked and hovering on those says "This plugin cannot be disabled, It has one more enabled dependants"
Which I don't really understand...the 'Enabled' boxes are greyed out unticked, but it says the plugin cannot be disabled.

And no, we can not enable the dependencies first:

all of the plugins are either greyed out enabled, or greyed out disabled; I can't change any of them.

 The dependencies look "a little circular" to me. I am not sure, whether that is seriously related.

Thanks in advance!

~J

P.S.

I am sorry I also posted this issue erroneously on "Jenkins Developers".

[lvot...@redhat.com]

Can you post which version of Jenkins you use and which plugins (if there are not too many)? 

[Wojtek]

Hi,

I've run today into exactly the same issue (Jenkins 1.656).

Basically it looks like the sate checking is wrong - I wasn't able to select "Static Analysis Collector Plug-in" but many required it (it was greyed out because of missing dependencies). I've fiddled a bit and found out that it's possible to enable/disable plugins by hand on the file system so I've tried removing ".disabled" suffix and... I ended up with a list of the plugins of which half is selected but greyed-out (and not working)... and what's even more weirder - now that "Static Analysis Collector Plug-in" is selected some plugins still complain that it's disabled, but now it's active so I can disable/uncheck it... and some other plugins are becomming active... but with "Static Analysis Collector Plug-in" *selected/enabled* they are greyed out and complain that static analysis plugin is... disabled!

I've looked for the solution but it feels like going circles.

[Daniel Beck]

This is a known issue on the configuration UI we're tracking as JENKINS-32340.

The workaround right now is to delete the files named PLUGINNAME.jpi.disabled in JENKINS_HOME/plugins, then restart Jenkins.

1: https://issues.jenkins-ci.org/browse/JENKINS-32340

> --
> 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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1edda12e-216f-4974-92f6-e6bbecbe02eb%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Wojtek]

I've run into this JENKINS-32340 page, but even when I delete all the
files with ".disabled" suffix and restart Jenkins the result is following:
- all plugins are enabled (have a tick next to the name)
- some of them (2/3 of the list) are still greyed out (inactive) which
basically means they are not loaded/funcioning.

Ticking some of those makes others change from "inactive" state (being
greyed out) to active (so I can check/uncheck them).

Bottomline, i looks like some circular dependency or somesuch


Wojtek

[Wojtek]

Actually I've played a bit with it and it looks like the plugins are enabled afterall - sorry for the confussion.

Wojtek

[Daniel Beck]

On 09.04.2016, at 10:19, Wojtek <woj...@unir.se> wrote:

> - some of them (2/3 of the list) are still greyed out (inactive) which basically means they are not loaded/funcioning.
>
> Ticking some of those makes others change from "inactive" state (being greyed out) to active (so I can check/uncheck them).
>
> Bottomline, i looks like some circular dependency or somesuch

Actually, that means you cannot disable them, because others depend on them. And disabling these other dependent plugins will allow you to disable their dependency. It's explained in the box that appears when hovering a disabled check box.