Every dish that leaves a good restaurant has been checked. CI/CD checks every change to software, automatically, before it reaches you.
In a well-run kitchen, every dish passes the head chef before it goes out. Too salty? Back it goes. Perfect? Off to the table.
CI/CD is that pass for software. Every time someone changes the code, robots automatically build it, run tests on it and, if it all passes, put it live.
The two halves
- CI, continuous integration: every change is combined with everyone else's and tested straight away
- CD, continuous delivery or deployment: changes that pass are ready to go live, or go live automatically
Why teams use it
Problems are caught minutes after they’re made, while they’re small and fresh in everyone’s mind. Nobody has to remember the release steps, because they’re automatic.
What it isn’t
It isn’t a guarantee nothing will break. It’s only as good as its tests. If nobody wrote a test for something, CI won’t check it.
Where the comparison breaks down
A chef tastes a few dishes. CI runs hundreds or thousands of checks on every single change, in minutes.
How the words fit together
A pull request triggers CI, which runs the build and tests. CD then deploys it. If something slips through, you roll back.
A red cross next to a change usually means CI found a problem. A green tick means all the automatic checks passed.
When you'll hear it
“CI is red.” The automatic checks failed, so the change isn't safe to use yet.
“It's in the pipeline.” The change is going through the automatic test-and-release steps.
“We have continuous deployment.” Every change that passes the checks goes live automatically.
“What do our automatic checks actually test? What still relies on someone remembering?”


