Building Your Continuous Delivery Toolkit
summary
Jenkins excels at build and CI but stretches badly when used as a one‑stop CD system, with 350 plugins and teams running 750 jobs that become hard to maintain. Practical toolkit pieces are: environment provisioning (CloudFormation, OpenStack Heat, jclouds), deployment automation (Rundeck, Fabric, mcollective, Docker, Cloud Foundry/OpenShift), test management (aggregate many tools, use context‑specific test selection like Google’s ML approach) and pipeline orchestration that handles manual steps, approvals and true production deployments.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:38How to think about building your Continuous Delivery Toolkit
- 5:32Challenges in Continuous Delivery
- 7:29What is Continuous Delivery
- 11:25What kind of tooling do you need
- 13:14Whats next
- 14:04Different Teams
- 15:41Customer Involvement
- 16:01Continuous Integration
- 20:36Environment provisioning
- 23:21Deployment
- 26:24Test Management
- 31:19Pipeline Orchestration
- 40:49Outro
related talks
45mBuilding Your Continuous Delivery Toolkit
45mBuilding Your Continuous Delivery Toolkit- 45mBuilding Your Continuous Delivery Toolkit
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
35mJenkins Scaling and Organization for an Efficient CI
24mWhy, What, and How of Continuous Delivery
27mAutomation, Innovation and Continuous Delivery
42mAutomation, Innovation and Continuous Delivery