Continuous Integration vs Continuous Delivery vs Continuous Deployment (ITIL® 5)
Preparing for the ITIL® 5 Foundation exam? CI/CD terms show up constantly around ITIL®, but they aren't native ITIL® vocabulary — they come from the DevOps and software delivery world. This guide clarifies the three terms and shows where they connect to ITIL® 5.
Quick Answer
Continuous Integration (CI) is the practice of developers frequently merging code into a shared repository, where automated builds and tests catch problems early. Continuous Delivery extends CI by automating the entire path to a release-ready build, but still requires a human decision to actually deploy to production. Continuous Deployment goes one step further and removes that human approval step entirely — any change that passes all automated tests is deployed to production automatically. These are DevOps and software delivery concepts, not official ITIL® terms, though they relate closely to ITIL®'s Release Management practice and the "optimize and automate" guiding principle.
Where These Terms Come From
Continuous integration, continuous delivery, and continuous deployment are not ITIL®-defined terms. They originate from the DevOps and agile software engineering world, describing increasingly automated approaches to getting code changes into production safely and quickly. ITIL® 5 doesn't invent or redefine them, but it does reference how ITIL® practices — especially Release Management and the "optimize and automate" guiding principle — interact with this kind of automated delivery pipeline.
Comparing the Three
| Continuous Integration | Continuous Delivery | Continuous Deployment | |
|---|---|---|---|
| What happens | Code is frequently merged and automatically built/tested | The full pipeline automates testing and prepares a release-ready build | Every change that passes testing is deployed automatically |
| Human approval to release? | N/A — this stage precedes release | Yes, required | No, not required |
| Goal | Catch integration problems early | Keep the codebase always releasable | Ship validated changes to users continuously |
How This Connects to ITIL® 5
ITIL®'s Release Management practice is concerned with making new and changed services and features available for use — deciding what goes live and when. CI/CD pipelines are one of the technical mechanisms that can feed into that decision: a continuous delivery pipeline gets a change release-ready, and Release Management (or an equivalent decision point) still determines when it's actually released. In organizations practicing continuous deployment, that decision point is automated rather than manual, but the underlying question — is this change validated and ready to reach users — still matters.
CI/CD is also a direct expression of the "optimize and automate" guiding principle: automating repetitive integration, testing, and deployment steps only pays off once the underlying process is well understood and optimized. Automating a messy, unreliable release process with CI/CD tooling just breaks things faster.
Real-World Example
A software team merges code into a shared branch multiple times a day, with automated tests running on every merge — that's continuous integration. The same team's pipeline also automatically packages, tests, and stages every validated change so it's ready to ship at any time, but a release manager still clicks "deploy" before it goes live — that's continuous delivery. A different team at the same company runs continuous deployment for a lower-risk internal tool: any change that passes automated tests goes straight to production with no manual approval step at all.
Why This Matters
Understanding these three terms matters because:
- The exam expects you to recognize DevOps/software delivery terms as distinct from official ITIL® terminology
- These concepts illustrate how ITIL® 5 explicitly acknowledges and works alongside DevOps practices, rather than competing with them
- They connect directly to Release Management and "optimize and automate," two frequently tested ITIL® concepts
Common Exam Mistakes
The most common mistake is assuming ITIL® invented or formally defines CI, CD, and continuous deployment. These are DevOps/software engineering terms that ITIL® 5 references and relates to, but doesn't originate.
A second mistake is confusing continuous delivery with continuous deployment. Continuous delivery always keeps a human decision point before release; continuous deployment removes it. The distinction is entirely about whether release still requires manual approval.
Memory Trick
Think:
Integration — merge and test.
Delivery — always ready, human hits go.
Deployment — no human needed, it just goes.
If there's still a manual approval gate before production, it's delivery, not deployment.
Key Takeaways
- Continuous integration, continuous delivery, and continuous deployment are DevOps/software delivery terms, not official ITIL® terminology.
- CI focuses on frequently merging and automatically testing code changes.
- Continuous delivery automates the path to a release-ready build but keeps a manual approval step before production.
- Continuous deployment removes that manual approval step, deploying validated changes automatically.
- These concepts connect to ITIL®'s Release Management practice and the "optimize and automate" guiding principle.
One Practice Question
Which statement best distinguishes continuous delivery from continuous deployment?
- Continuous delivery requires no automated testing, while continuous deployment does.
- Continuous delivery keeps a manual approval step before production release, while continuous deployment removes it and deploys automatically.
- They are identical terms used interchangeably in ITIL®.
- Continuous deployment is an official ITIL® practice, while continuous delivery is not.
Show Answer
Correct Answer: B
The defining difference is whether a human approval step remains before production release — continuous delivery keeps it, continuous deployment automates past it. Neither term is official ITIL® terminology.
Frequently Asked Questions
Are CI, CD, and continuous deployment official ITIL® terms?
No. They come from the DevOps and software engineering world. ITIL® 5 references and relates to them, particularly through Release Management and "optimize and automate," but doesn't define them itself.
What's the actual difference between continuous delivery and continuous deployment?
Continuous delivery keeps a manual approval step before a change goes to production. Continuous deployment removes that step, deploying any change that passes automated tests without human intervention.
How does CI/CD relate to ITIL®'s Release Management practice?
Release Management decides when a change is made available for use. CI/CD pipelines are a technical mechanism that can prepare and, in continuous deployment, even execute that release automatically.
Is this topic tested on the ITIL® 5 Foundation exam?
Yes, as part of understanding how ITIL® 5 relates to DevOps practices and the "optimize and automate" guiding principle.
Ready to Test Yourself?
Now that you understand CI, CD, and continuous deployment, the next step is seeing how these ideas fit into the broader ITIL®-DevOps relationship. Take our free diagnostic quiz at PassTheFoundation.com to test yourself, or continue exploring the other ITIL® 5 core concept guides.