Jonathan Lebon

Let's repurpose this to go a step further and lock down all our plugins and the base Jenkins version itself and e.g. have a job that opens a PR to...

This needs to account to the different clusters we support being different versions (and thus having different Jenkins base versions). We could choose to track the older of the two,...

Was chatting with @marmijo about this today. One suggestion is to have the job on the prod Jenkins instrument the Jenkins on the stage cluster. Something like: 1. Clone repo,...

How many dependencies in the base list were updated?

> There were 7 dependencies already installed by `base-plugins.txt` I'm not sure if this answers my question or not. Let me ask a different way: in the resulting image, for...

OK that's great. I think this could be a viable path forward then. For the record, what I was worried about was how much drift we'd be introducing in the...

> Checked with the Openshift team on the reason why the the `resolveDependency` function was disabled. > > Apparently they had several issues with the `resolveDependency` plugin resolution which gave...

OK, looks like Jenkins has an API for installing/updating plugins: `$JENKINS_URL/pluginManager/installNecessaryPlugins` (see the docs at `$JENKINS_URL/pluginManager/api/`). You can do a POST with some XML and it'll install the plugins. See...

I think a lot of the code in #917 is still necessary. The main bit is how we construct the new `plugins.txt` would now come from Jenkins itself. Maybe we...

Met with @aaradhak and @marmijo. We're reducing the scope of this to just opening a PR with the updated plugin versions. This little bit of automation is still helpful since...