Scaling Jenkins
summary
Scaling a Jenkins deployment for continuous integration at Camunda, where the largest Jenkins server runs over 2,500 jobs, using Kubernetes and Google Cloud. Covers organizational, performance, and scalability challenges encountered, evaluates different solutions, and presents the deployment model and best practices the team found most successful for balancing developer freedom and infrastructure control.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 4:15Company and Jenkins history
- 8:40From Hudson to scaling
- 10:29Virtual machines and early scaling
- 13:26Isolation issues and containers
- 16:30Container limits and solutions
- 19:19Cloud migration and Kubernetes
- 22:22Configuration as code
- 25:49Automation and project generation
- 27:15Current Jenkins scale
- 28:44Team autonomy vs control
- 31:13Migration to Kubernetes
- 33:01Q&A
related talks
35mJenkins Scaling and Organization for an Efficient CI
55mContinuous Integration on Steroids
23mMoving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD
28mGrowing Pains - Scaling Jenkins in the Federal Sector
38mOperating Jenkins at Scale
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
37mHelping Enterprises Scale Their Jenkins Software Practices and Tools
44mScaling Your Jenkins Jobs