4 ms·
I think most people do. We did a couple of things to get out of that state at Conjur. First, we made all of our builds into docker containers. Under this sys
by onetwotree 11y ago
I think most people do. We did a couple of things to get out of that state at Conjur.
First, we made all of our builds into docker containers. Under this system, slaves (we call 'em executors now) only contain very basic software - docker, git, and make to be specific. This means that our builds are entirely self contained, and we don't have to worry about, for example, messing around with RVM on executors. If the containerized build works locally, it pretty much always works on Jenkins as well.
Second, we started using the job dsl plugin to manage configuration and brought in some autoscaling and machine identity. Beyond what I do as a platform engineer to turn my projects into jenkins builds, I don't completely understand it (nor do I have to, which is a good thing!), so I'll let our DevOps guy take it from here:
https://blog.conjur.net/scaling-jenkins-with-machine-identity https://blog.conjur.net/scaling-jenkins-with-machine-identit...
- jacques_chester 11y agoYou might like to look at Concourse[1], which makes explicit, checked-in pipelines of containerized builds its central model. I am very bullish on Concourse. [1] https://concourse.ci https://concourse.ci