4 ms·
Trying to integrate Jenkins w/ Github Enterprise proved to be a real pain for me. It wasn't clear what git* plugin is the best to use for how I wanted to setup
by linuxftw 8y ago
Trying to integrate Jenkins w/ Github Enterprise proved to be a real pain for me. It wasn't clear what git* plugin is the best to use for how I wanted to setup builds. It's literally impossible to deploy Jenkins in a repeatable manner with just configuration files, you must get it online and use the api to configure such simple things as API keys (eg, specify the ID of the key so your jobs actually reference the key and don't break).
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.
- mathewpeterson 8y agoYou definitely can configure Jenkins in a repeatable manor. See https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script 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/blob/master/README.md https://github.com/jenkinsci/configuration-as-code-plugin/bl...
- linuxftw 8y agoI 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.