Building Your Continuous Delivery Toolkit
summary
Explains why Jenkins remains core but not sufficient, and lays out a concrete CD toolkit across CI, deployment, scaling, testing and release management; calls out real plugins used — build failure analyzer, promoted builds, build monitor, swarm plugin — and operational problems: who maintains Jenkins and plugins, automated database scripts and tests, environment scaling, and cross-team visibility for QA, DBAs, ops and the business. Emphasizes practical integration patterns and where Jenkins should hand off to other best‑of‑breed tools.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:07Why are we discussing other tools
- 2:50Using Jenkins plugins
- 5:30When to start thinking about other tools
- 6:28The onion of continuous delivery
- 8:32How to productionalize your Toolkit
- 11:06Technical Needs
- 12:19Continuous Integration
- 14:16Common Challenges
- 17:17Reality of Deployment
- 20:13What Should Our Toolkit Look Like
- 22:01Scaling
- 28:51Testing
- 32:45Testing Tools
- 36:44Release Management
- 40:20Tools
related talks
42mBuilding Your Continuous Delivery Toolkit
45mBuilding Your Continuous Delivery Toolkit- 45mBuilding Your Continuous Delivery Toolkit
24mWhy, What, and How of Continuous Delivery
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
23mKeynote: The Past, Present and Future of Continu...
27mAutomation, Innovation and Continuous Delivery
24mContinuous Delivery