Building Your Continuous Delivery Toolkit
summary
Jenkins is useful for build and CI but fails at end-to-end delivery problems that need specialized tools: environment provisioning (Terraform, CloudFormation, OpenStack Heat, Docker), app deployment patterns (virtual‑appliance vs platform/PaaS), test-management for aggregating flaky/volume tests, and multi-machine orchestration for blue‑green/canary rolls. Real examples: a deployment tool targets ~50 middleware variants, and ~75% of apps fit a cookie‑cutter deploy model. If the pipeline needs environment provisioning, multi-machine orchestration, test aggregation or customer‑facing release status, add best‑of‑breed tools beyond Jenkins.
AI-written summary · about
chapters (12)
- 0:00Introduction to CD
- 2:54Tooling and the CD lifecycle
- 6:15Layers of CD complexity
- 10:48Essential pipeline components
- 14:26Business goals and CD
- 17:43People and organizational roles
- 20:28Continuous integration
- 23:54Environment provisioning
- 26:07Deployment strategies
- 32:16Test management and logic
- 36:21Pipeline orchestration
- 41:43Adopting a toolset
related talks
45mBuilding Your Continuous Delivery Toolkit
42mBuilding Your Continuous Delivery Toolkit
45mBuilding Your Continuous Delivery Toolkit
24mWhy, What, and How of Continuous Delivery
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
27mAutomation, Innovation and Continuous Delivery
30mA Journey Introducing Jenkins to Enterprise IT