> On 04.05.2016, at 12:48, Paulo Moreira <[email protected]> wrote: > > +1 fixed thanks :) > > cd /var/lib/jenkins/plugins > ls -la | grep disable > > if files rm > > Did the trick!
FWIW we included a change in 2.1 that results in new plugin installations no longer causing this problem: Disabled dependencies are now automatically enabled, similar to how dependencies that aren't installed get installed. So unless you mess around with the plugins/ directory directly, admins should be protected from this situation for any plugin installation. -- 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/70352362-D3B5-4315-8190-A23DA90ECEBD%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
