The Pipeline Driven Organization｜
summary
Argues that a Pipeline Driven Organization moves tactical decisions into a single automated pipeline so deployments happen in minutes not months, with delegates encoded as tests that veto by returning a non zero exit code. Describes concrete tools and files to edit: Jenkins file, Docker and Kubernetes for per‑commit environments, Terraform and CircleCI examples, and a practice called a test recipe that specifies layered tests and confidence metrics (1–5) to measure progress.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:48Continuous Delivery vs Continuous Integration
- 4:45The Pipeline Driven Organization
- 7:48Waterfall vs Pipeline Driven Organization
- 13:55How do we trust pipelines
- 15:00Pipeline delegates
- 15:33Pipeline decisions
- 17:42Pipeline skills
- 18:02Pipeline transformation
- 20:54Security
- 22:30Testers
- 24:54Skills
- 26:07Developers
- 33:47Test Architects
- 42:53Cooperative pipelines
related talks
41mThe Pipeline-Driven Organization
44mQA in a Pipeline Based Organization
45mBecoming a Plumber: Building Deployment Pipelines
28mThe DevOps Pipeline
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
34mFrom Code to Deployment: A Deep Dive into Pipelines as Code
49mOne pipeline to rule them all
59mNow That My Delivery Pipeline Is in Place, What About My Organization?