Supercharged Continuous Integration with Docker Containers
summary
Using unprivileged Docker containers for Jenkins agents, with per-build custom images that include language runtimes and dependencies, speeds up CI, provides true isolation, and enables developers to reproduce the CI environment locally. A pilot integrated these containerized agents into an existing Jenkins farm and reduced flaky integration failures and debugging time while allowing local reproducible builds that match CI.
AI-written summary · about
chapters (11)
- 0:00CI system
- 2:30Jenkins evolution
- 6:50Isolation problems
- 9:18Jenkins limits alternatives
- 11:16Docker discovery Slayer tests
- 13:01Unprivileged containers
- 15:58Docker isolation benefits
- 18:05Faster reliable builds
- 20:40Lessons learned
- 23:38Private cloud delegation
- 26:06Conclusion
related talks
30mContinuous Integration; Tips & Tricks
13mEvolution of containers in continuous integration
06mBuilding Continuous Delivery Pipelines
43mLightweight PaaS for Jenkins CI Environments with Docker
41mContinuous Integration Tips & Tricks
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
42mHow Containerized Pipelines Can Boost Your CI/CD