> On 3. Nov 2017, at 02:17, CLOSE Dave <dave.cl...@us.thalesgroup.com> wrote: > > I think part of the trouble with the seemingly endless dependency chain > may be the Pipeline plugins. Most if not all of the other plugins seem > to define the other plugins on which they are dependent. The Pipeline > plugins, in contrast, define only the other plugins which depend on them.
Not really -- plugins always define what they depend on, not the other way around. In this case, the 'Pipeline' aggregator plugin depends on Declarative Pipeline. 'Pipeline' itself has no functionality, it just aggregates all 'default' Pipeline functionality. If you're not using Declarative (or even Pipeline), I'd start disabling things there. (On the plugins manager UI, disabling plugins enables checkboxes of plugins that can then be disabled because nothing else depends on them, etc. -- much easier than deleting one by one.) -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/B26F9A82-8346-460D-9100-D108DCC00E31%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
