| Hi, to respond in context, I am just another user also struggling w/plugin mgmt. Initially I was not aware of other's efforts at a different solution, hence shared the Plugin Installation Manager Tool reference. It is a modest improvement of install-plugins.sh We use standalone war in multiple instances in an Enterprise environment (100's users, 1,000's jobs), leverage customized install-plugins.sh from Docker source. Config Initially w/init.groovy.d, now added JCasC. Our jenkins.conf, jenkins.sh, plugins.txt, init.groovy / jcasc.yaml all checked into mgmt repo which we pull, then launch. JCasC made life much easier, but JEP-201 is still an (excellent) Work in Progress, with exciting enhancementsJEP-208 to come. Works well, but we yearn for more/better/simpler as do others, especially eg: if the plugins list does not match the config list or vice versa! I understand there are added issues using via Docker Image in a complex environment. I would love to see JCasC built into Core or extended as you suggest so that it accepted a plugins list as described. I expect there may be hurdles eg: JENKINS-51856, managing explicit vs dependent plugins,ver. compatibility, Dockerized or not, etc. Ideally for me, the (built-in) JCasC mechanism would just read, "with plugin (opt. +ver.), this configuration" then, if the plugin was missing, retrieve it, then configure. +1 for your issue; let's see where the maintainers go with it. |
