CI/CD Course
Continuous Deployment
In this lesson
Continuous Deployment is the practice of automatically releasing every code change that passes all pipeline checks directly to production — with no human approval step. Where Continuous Delivery keeps a human in the loop for the final release decision, Continuous Deployment removes that gate entirely. The pipeline is the gatekeeper. If it passes, the change ships. Every time. Automatically.
This is the most aggressive form of CI/CD, and it is also the most misunderstood. It is not reckless — teams that practise it successfully are among the most disciplined engineering organisations in the world. Continuous Deployment is not about removing safety; it is about relocating safety from a manual human check to a comprehensive automated system. This lesson explains what that system must look like and when the practice is — and is not — appropriate.
The Key Difference from Continuous Delivery
The distinction is a single gate. In Continuous Delivery (Lesson 5), a human reviews the pipeline results and clicks to approve the production release. In Continuous Deployment, that click does not exist. The pipeline itself makes the release decision by running a comprehensive set of automated checks — and if every check passes, the deployment proceeds without waiting for anyone.
Continuous Delivery vs Continuous Deployment — Side by Side
The Prerequisites: What Must Be True Before You Remove the Gate
Continuous Deployment is only safe if the automated system that replaces the human gate is genuinely trustworthy. Teams that adopt it prematurely — before the prerequisites are in place — ship broken code to production automatically and at speed. The prerequisites are not suggestions. They are the minimum conditions under which removing the approval gate is responsible.
Prerequisites for Continuous Deployment
The Autopilot Analogy
Commercial aircraft autopilot does not make flights reckless — it makes them safer and more consistent than manual flying for long stretches. But autopilot only works because the aircraft is instrumented to detect deviations instantly, the pilots remain alert and ready to intervene, and the system disengages automatically the moment something unusual is detected. Continuous Deployment works the same way: it replaces manual oversight with automated instrumentation, continuous monitoring, and rapid intervention capability. Remove any of those and it is no longer safe to hand control to the machine.
What Continuous Deployment Looks Like in Practice
The best way to understand the practice is to follow a change from commit to production at a team that does it well. The numbers below are representative of mature organisations like GitHub, Etsy, and Flickr, all of which have published engineering accounts of their Continuous Deployment practices.
Commit to Production — Fully Automated
v3.88.2. Deployed automatically to staging. Integration and end-to-end tests run.v3.88.2 is deployed to production. Monitoring dashboards update. Error rate nominal. Latency unchanged.The Numbers: What Continuous Deployment Makes Possible
Continuous Deployment is not a theoretical ideal — it is standard operating procedure at some of the largest engineering organisations in the world. The scale at which these organisations deploy is a direct result of removing the human bottleneck from the release process.
50+
Deployments to production per day at Amazon — each one automated, each one monitored
< 15 min
Typical commit-to-production time for teams running mature Continuous Deployment pipelines
< 1 hr
Mean time to restore after a production incident for elite DORA teams using automated rollback
0.1%
Change failure rate achievable by mature teams — 1 in every 1,000 deployments causes an incident
When Continuous Deployment Is Not the Right Choice
Continuous Deployment is not universally appropriate. There are legitimate organisational, regulatory, and product constraints that make the approval gate in Continuous Delivery the correct choice. Choosing Continuous Delivery over Continuous Deployment is not a sign of immaturity — it is a sign of understanding your context.
Situations Where Continuous Delivery Is the Better Choice
Warning: Continuous Deployment Without Monitoring Is Just Fast Failure
The most dangerous configuration in software delivery is Continuous Deployment paired with weak production monitoring. When a bad change ships automatically and there is no alert to detect it, the damage accumulates silently — sometimes for hours — before someone notices. Continuous Deployment makes monitoring non-optional. If your team cannot detect a production regression within minutes of it occurring, you are not ready to remove the approval gate. Build the observability layer first.
Key Takeaways from This Lesson
Teacher's Note
Before debating whether to adopt Continuous Deployment, answer this first: "If a bad deployment went to production right now, how long before we'd know?" If the answer is more than five minutes, fix your monitoring before touching the approval gate.
Practice Questions
Answer in your own words — then check against the expected answer.
1. What mechanism allows a team to ship code to production in a disabled state and then gradually enable it for a percentage of users — decoupling deployment risk from feature risk?
2. What system must be in place to ensure that when a bad change reaches production automatically, the team detects it within minutes rather than hours?
3. What is the single element that Continuous Deployment removes that Continuous Delivery retains — the step where a human reviews automated results before the production release proceeds?
Lesson Quiz
1. A manager argues that Continuous Deployment is reckless because it removes human oversight. What is the accurate reframing of what Continuous Deployment actually does?
2. A team uses Continuous Delivery but their release manager spends 30 minutes manually testing every build before approving it. What does this reveal?
3. A healthcare software team has a fully automated build, test, and staging pipeline but is required by HIPAA compliance to have a documented human approval before each production release. Which practice should they use?
Up Next · Lesson 7
CI vs CD
Now that you know what each practice means individually, learn how CI and CD fit together as a unified system — where one ends, the other begins, and why the boundary matters.