CI vs continuous delivery vs continuous deployment?
Understand the concept
Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.
Important ideas
-
CI builds and checks changes automatically.
-
Continuous delivery keeps a tested release ready; production release may be manual.
-
Continuous deployment automatically releases changes that pass the required checks.
-
A manual approval gate can be part of continuous delivery without undermining the value of automated validation.
Can you explain it without the notes?
CI vs continuous delivery vs continuous deployment?
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.
Turn this concept into a clear answer.
- Explain the project's actual release gates and rollback mechanism instead of using CI/CD as one vague term.
Adapted from 09_TESTING_GIT_DOCKER_CLOUD.md · “CI vs continuous delivery vs continuous deployment?”. Examples are study fragments; framework behavior can depend on your version.