Automation, Innovation and Continuous Delivery
summary
Continuous Delivery with Jenkins automates builds from every GitHub commit into one pipeline per product, runs unit/integration tests, publishes Docker images to S3 and deploys Docker -> Elastic Beanstalk with non‑downtime swaps, and notifies teams via HipChat/Slack; logging captures 23 million events and monitoring uses New Relic; operations accept blameless postmortems, developers who push code are on call, and around ~38 feature flags control rollout while CloudBees hosts Jenkins.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:24Automation drives innovation
- 7:16Trust through developer freedom
- 13:16Culture beats strategy
- 16:46Core business over infrastructure
- 18:09Data beats gut feelings
- 20:33Mandatory vacations for quality
- 21:57Big releases riskier than daily
- 22:58Feature flags for safe delivery
- 25:00Pipeline from commit to production
- 26:47Docker and cloud scaling
related talks
42mAutomation, Innovation and Continuous Delivery
27mAutomation, Innovation and Continuous Delivery
24mWhy, What, and How of Continuous Delivery
38mAccelerating innovation through AWS Cloud technology
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
34mContinuous Delivery with Jenkins Workflow
35mJenkins Scaling and Organization for an Efficient CI
42mJenkins: Enabling Agility and Efficiency