Re:Jenkins Is Getting Old
by mathewpeterson on Monday April 29, 2019 @04:49PM
(#19782473)
You definitely can configure Jenkins in a repeatable manor. See https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script
You can write all the configuration in groovy and it will execute when the Jenkins process starts up.
There is also "Jenkins Configuration as Code" plugin which allows you to have a single yaml file to configure most of the Jenkins system.
https://github.com/jenkinsci/configuration-as-code-plugin/bl...
I managed to accomplish the task at hand ~2.5 years ago, so yes, it's possible to deploy jenkins in a repeatable manner.
I guess what I'm driving at is that it's not very declarative and it's cumbersome.
Another big pain point, for me was, no obvious openstack integration. I wanted my jobs to run on ephemeral instances so all my dependencies could be defined in the job themselves, not having to rely that the Jenkins worker is setup just right.
I think Gitlab runners get this right, but I have not investigated too far.