Evolution of Continuous Integration/Continuous Delivery with...
summary
Overview of how Continuous Integration and Continuous Delivery practices have evolved as container technologies emerged, focusing on containers (e.g., Docker) and their impacts on CI/CD workflows and tooling. Presents changes in build, test, deployment pipelines and how container evolution influences automation and delivery approaches, based on CloudBees' perspective.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:45Daft Punk effect on devs
- 3:30Continuous Delivery principles
- 5:37Jenkins traditional limits
- 8:28Jenkins plugin chaos
- 9:55Build Flow plugin benefits
- 11:20Jenkins info dispersion
- 12:43Jenkins pipelines evolution
- 16:36Workflow plugin advantages
- 17:38CI/CD as Code with Jenkinsfile
- 19:24Multibranch pipeline automation
- 21:50Docker in CI/CD pipelines
- 25:17Docker security challenges
- 26:41Docker Pipeline plugin
- 28:25CI/CD with Docker Slaves
- 31:34Declarative pipelines experiments
- 33:40Declarative pipelines pros/cons
- 35:28Blue Ocean visualization
- 37:14Docker persistent volumes
- 38:38Core containers future
- 40:02Q&A
related talks
24mWhy, What, and How of Continuous Delivery
13mEvolution of containers in continuous integration
22mPushing the Limits of Continuous Delivery
42mHow Containerized Pipelines Can Boost Your CI/CD
23mKeynote: The Past, Present and Future of Continu...
19mModern Continuous Delivery
34mContinuous Container Integration for Containers
01h 32mScaling Your Continuous Deployment using Docker and Containers