Continuous Integration on Steroids
summary
A case study of one of the largest monolithic Jenkins installations, describing a single master handling over 100,000 builds per day and up to ~2,500 executors. Covers deploying CI in the cloud, using memcache to reduce hardware costs, Jenkins performance limits, plugin tips (which help and which hurt), whether to monitor Jenkins GC, and building Jenkins monitoring with FluentD + InfluxDB + Grafana.
AI-written summary · about
chapters (18)
- 0:00Introduction to CI
- 1:06Talk outline
- 3:15CI system requirements
- 7:12CI system monitoring
- 11:29CI scaling goals
- 13:15CI scaling methods
- 16:51Test and cache optimization
- 18:34Jenkins role in CI
- 19:16Jenkins issues and fixes
- 23:07Jenkins log problems
- 25:14Build history issues
- 26:18S3 artifact storage
- 27:02Jenkins plugin problems
- 31:44Jenkins performance tuning
- 36:02Jenkins max load
- 38:08Key takeaways
- 42:01Q&A
- 54:38Summary
related talks
46mMonitoring a Cloud CI System: The Jenkins Example
38mOperating Jenkins at Scale- 38mOperating Jenkins at Scale
35mJenkins Scaling and Organization for an Efficient CI
41mScaling Jenkins
42mSeven Habits of Highly Effective Jenkins Users- 42mSeven Habits of Highly Effective Jenkins Users
47mJenkins in the Enterprise: Building Resilient CI Infrastructure