📖 Business
Deployment Pipeline
The deployment pipeline is the central abstraction in continuous delivery: a fully automated process that takes every commit from check-in through build, test, and deploy stages until it either proves itself production-ready or fails visibly. Every commit is treated as a release candidate. The pipeline's job is to disprove that assumption as quickly and cheaply as possible — or confirm it with increasing confidence at each stage. If any stage fails, the pipeline stops, the team is notified, and nothing moves forward until the problem is fixed. This is the single most important technical practice separating high-performing delivery teams from everyone else.
2
Minutes
2
Concepts
+45
XP
1
How It Works
The pipeline has four progressive stages, each more expensive and more thorough:
Stage 1: Commit Stage (~5 minutes)
- Compile, run unit tests, perform static analysis
- Fast feedback — catches obvious breakage within minutes
- If this fails, the developer who committed fixes it immediately
Stage 2: Acceptance Stage (~30-60 minutes)
- Deploy to a staging environment automatically
- Run acceptance tests written in business language against real requirements
- Validates that the software does what stakeholders actually asked for
Stage 3: Performance/Capacity Stage
- Load testing, stress testing, soak testing
- Validates nonfunctional requirements (response time, throughput, resource usage)
- Catches problems that only appear under realistic production load
Stage 4: Production Deploy
- Push-button, fully automated deployment
- No manual steps, no SSH, no crossing fingers
- The deploy itself is a tested, repeatable script
Key principles: every stage increases confidence. Earlier stages are fast and cheap; later stages are slow and thorough. The pipeline is the single source of truth for whether a commit is releasable.