Evolution of containers in continuous integration
summary
Describes modernizing a legacy CI setup (physical CentOS/Debian/Windows agents and fragile Jenkins freestyle jobs) by standardizing builds with Docker so tests start in seconds, moving CI logic into Jenkins Pipeline and Pipeline Shared Libraries to simplify and centralize pipeline code, and handing orchestration to Kubernetes so deployments can scale and tear down automatically. Reports a Jenkins plugin reaching ~180,000 installations, reducing pipeline code to a single build call and producing faster tests, lower maintenance, and more reliable releases.
AI-written summary · about
chapters (8)
- 0:00Containers in CI
- 1:31Introduction
- 5:27Desktop to CI pipelines
- 7:58Early CI limits
- 9:45Docker revolution
- 10:48Kubernetes and shared libs
- 11:54Modern CI benefits
- 12:17Q&A
related talks
06mBuilding Continuous Delivery Pipelines
35mJenkins Scaling and Organization for an Efficient CI
30mContinuous Integration; Tips & Tricks
34mContinuous Delivery with Jenkins Workflow
38mUsing Containers for Continuous Integration and Continuous Delivery [I]
28mSupercharged Continuous Integration with Docker Containers
25mContainer pipeline for devs and enterprises alike!
35mOptimizing Your CI: Lessons Learned from a Successful Jenkins Rebuild