Continuous Integration (CI) vs Continuous Delivery (CD)
People think CI and CD are one step, because they are written together as CI/CD, and they are not. CI checks each change: it builds the code and runs the tests on every push. CD comes after it and takes a passing change toward the live site. You can have CI with no CD, but not CD with no CI.
Continuous Integration (CI)
Merging code often. A machine builds and tests each change.
Continuous integration means merging code often and letting a machine check each change. When someone pushes code, a server builds it and runs the tests. If anything fails, the team knows within minutes. Small changes merged daily are easy to fix. Big changes merged once a month clash badly.
Continuous Delivery
Keeping code ready to release at all times. Going live is one click.
Continuous delivery means your code is always ready to release, at the push of a button. Every change that passes the tests is built and sent to staging on its own. Going live is one click, but a person still decides when. Releases become small and boring, not big and scary. It is the step after CI.
In one line
- Continuous Integration (CI)
- Merging code often. A machine builds and tests each change.
- Continuous Delivery
- Keeping code ready to release at all times. Going live is one click.