Failed Loading plugin Pipeline v2.6 (workflow-aggregator) about jenkins-debian-glue

[upMKuhn]

I honestly replied to this issue without properly reading it.
My setup is based on the K8S Jenkins Operator. The Jenkins container failed to start, because the Pipeline v2.6 (workflow-aggregator) plugin and others failed to be installed. Within 200 error messages I eventually found Configuration as Code Plugin (1.29) to be updated to 1.35 or higher. I followed the advice and upgraded this and a few other plugins . Boom it worked perfectly.

So maybe this issue shares a similar root cause of out dated dependent plugins.

[CyrilBrulebois]

Since my use case isn't exactly a direct use of the jobs as set up by jenkins-debian-glue (I'm mostly using Pipeline: Multibranch jobs but relying on jenkins-debian-glue binaries/helpers), I've decided to disable most plugins, and only keep a handful where names sounded security-relevant. Which means keeping these:

[
 'credentials',
 'icon-shim',
 'ssh-credentials',
 'script-security',
 'structs',
]

(structs version 1.7 can be documented as a dependency of Credentials Plugin version 2.2.1)

And while writing this comment, I realized the absence of setup wizard is normal, just due to the config.xml put in place by the jenkins::config class (which I ended up disabling), so that's not a consequence of issues with plugin dependencies… I'm posting this comment anyway, in case someone else needs a minimal amount of plugins to base their work on. ;)

[default-work]

[
'credentials',
'icon-shim',
'ssh-credentials',
'script-security',
'structs',
]

@CyrilBrulebois Hi, will you make tips or guidelines how to remove all plugins on my Ubuntu 16.04, using command line, bash nano or Web UI, i cant figure this out

[mika]

@CyrilBrulebois yeah, the dependencies of the plugins can't be handled and we need to track all of this manually :-/ I try to keep the plugin setup working for everything that's supposed to work OOTB from j-d-g's perspective and its provided example jobs. I am afraid everything else needs to be handled by the operator (unless someone comes up with a proper solution for handling Jenkins plugin and its dependencies), though this is usually easy to fix from within the web interface of Jenkins at least for now.

The Pipeline plugin and all its dependencies are kind of impossible to keep up2date with the infrastructure we currently rely on, but we don't use it in any of the provided j-d-g Jenkins jobs. Visiting Jenkins UI and clicking "Correct" should be the easiest fix for this:

@funcelotwork I've no idea what you're actually trying to achieve, probably you're looking for $JENKINS_URL/pluginManager/?

[upMKuhn]

I encountered the same issue. The reason was Update required: Configuration as Code Plugin (1.29) to be updated to 1.35 or higher

[mika]

@upMKuhn just to clarify, it's only about the Pipeline plugin or some other plugin that j-d-g doesn't really rely on, right?