CI vs continuous delivery vs continuous deployment?
Practice this questionWANT TO UNDERSTAND THE CONCEPT FIRST?Learn CI vs continuous delivery vs continuous deployment?
Definition:
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.
Key points:
-
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.
Interview point:
- 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?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.