What Is Continuous Deployment?
Continuous deployment automatically releases every change that passes the pipeline straight to production, with no manual approval step.
Continuous deployment is the most automated rung of the CI/CD ladder. It takes continuous delivery one step further: instead of a human deciding when to release, any change that survives the full set of automated checks goes live on its own.
The defining trait
There is no manual gate before production. The pipeline is the gate. If the build, tests, and any other checks pass, the change deploys automatically, often within minutes of merging. This only works when the automated checks are trusted enough to stand in for human judgment.
How it works
- A change merges to the main branch.
- The pipeline builds and runs the full test suite.
- Additional gates run: integration tests, security scans, smoke tests.
- On success, the change deploys to production automatically.
- Monitoring and automated rollback catch anything that slips through.
An example
A developer merges a small UI fix at 2pm. By 2:06pm the pipeline has built it, run thousands of tests, deployed it behind a canary, watched error rates for a few minutes, and rolled it out to all users, with no human in the loop after the merge.
The safeguards it needs
Removing the human gate raises the bar for everything else. Continuous deployment leans heavily on comprehensive automated tests, progressive rollout strategies like canary deployments, strong monitoring, and fast automated rollback. Feature flags let risky changes ship dark and be enabled separately.
When it fits
Continuous deployment shines for web services where rolling back is cheap and rollout is gradual. It is less suitable where a release is hard to reverse, such as firmware or some regulated systems. Many teams adopt it for some services and keep a manual gate for others.
Key takeaways
- Continuous deployment ships every passing change automatically.
- It demands strong tests, monitoring, and fast rollback.
- It suits services where rollout is gradual and rollback is cheap.