Every development team wants to have their own Jenkins instance and “all the resources”. How can this be administered - especially if you have more than 200 Jenkins instances?
This talk shows how Jenkins master instances can be provisioned and custom tailored in seconds, while admin and upgrade overhead stays reasonable. We will also talk about quotas to fairly distribute resources and avoid teams affecting each other. Whether you are a release engineer or developer of an Eclipse project or a Jenkins administrator at your company, this talk is for you.
The Eclipse Foundation provides a dedicated build infrastructure for it’s member projects. In quest of the best solution we have switched to a custom-tailored full OSS approach based on Docker, Openshift, the Jenkins Configuration as Code Plugin and a few scripts.
This talk will also cover lessons learned and the status quo of our migration efforts to our new infrastructure. Last but not least, we will touch upon common problems and solutions when working with docker based Jenkins agents in a Kubernetes environment.