Building Your Continuous Delivery Toolkit
summary
Jenkins handles build and CI well but is not a silver bullet so expect to compose a toolkit: use Jenkins sweet spot for merge and unit stages, add provisioning like Terraform CloudFormation or Docker/AMI for environments, use orchestration that supports blue green and canary deployments and multi‑machine choreography, add test aggregators for Selenium Gatling Cucumber and address the data glue problem that wires outputs between tools. Real example: an installation runs matrix tests across 50 middleware targets and works but stretches Jenkins beyond its core.
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
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
35mJenkins Scaling and Organization for an Efficient CI
24mWhy, What, and How of Continuous Delivery
34mContinuous Delivery with Jenkins Workflow