I've been trying to figure out clean solutions to the ci.blueocean docker image having the latest master code, but actually having all its dependencies properly.
My plan was to install blueocean using jenkins:lts and install-plugins, then overwrite them with master built images.
That works pretty good, but when blueocean required new deps, things got weird and didn't auto update properly, which left a docker image that didn't work without manual intervention.
I started to look into install-plugins.sh loading incrementals, which seems like it should work. But I'm not sure I can easily and safely figure out which is the latest master. Right now i'm using blueocean:incrementals;io.jenkins.blueocean;1.18.0-rc4039.8404684f7813 in my plugins.txt, but I think thats a specific snapshot. I figured from the docs that mvn incrementals:updatePluginsTxt -DpluginsFile=plugins.txt should work, but it kept erroring out (I just just realized as typing that its because there's no pom.xml to say where to get the incrementals prefix, mvn incrementals:updatePluginsTxt -DpluginsFile=plugins.txt does work).
Is the maven step the right way to get latest master in your plugins.txt?
So
1) is there a solution for above to actually get the right plugin and deps?
2) Is there any reason install-plugins is a bash shell script? and not a jar file with the relavent update center type classes that does all the resolving the same as the main application does?
Gavin