continuous deployment
Automatically releasing every change that passes the pipeline to production, with no human approval step.
In more detail
Continuous deployment removes the final manual decision that continuous delivery keeps. It only works when tests, monitoring and rollback are trustworthy, because nobody looks at a change before users receive it.
Related terms
- continuous delivery — Keeping every change that passes the pipeline in a state where it could be released to production at any moment.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- rollback — Returning a system to a previous known-good version after a bad change.
- blast radius — How much of a system is affected when something fails or has to be running for a check to happen.
Taught in
- An Hour Without Payments: Continuously Reconciled — Certified GitOps Associate (CGOA) Exam Prep
- What Does CI Still Do? CI, CD And Where GitOps Starts — Certified GitOps Associate (CGOA) Exam Prep
- Related Practices Sprint: One Change, Five Practices — Certified GitOps Associate (CGOA) Exam Prep
- Forty-Six Of Sixty: The Mock And What It Tells You — Certified GitOps Associate (CGOA) Exam Prep
- What Is a Pipeline? — Continuous Integration & Continuous Delivery Pipelines
- Continuous Delivery Versus Continuous Deployment — DevOps & Site Reliability Engineering
- Continuous Integration, Delivery And Deployment: One Keyword Apart — GitLab Certified CI/CD Associate Exam Prep