CI/CD

CI vs CD vs Continuous Deployment

Untangle three terms that get blurred constantly.

25 min read beginner 3 objectives

Status

Not started

What you will learn

  • Define CI, delivery, deployment
  • Map them to a workflow
  • Know the value of each

New to this? Start here

The basics, in plain English

CI/CD is about automating the boring, risky steps between writing code and getting it to users. Instead of a human manually testing and deploying, a pipeline does it the same way every time. CI checks your code; CD ships it.

CI (Continuous Integration)
Automatically building and testing your code every time you push a change.
CD (Continuous Delivery)
Automatically preparing every change so it is always ready to release with one click.
Continuous Deployment
Going one step further: every passing change ships to users automatically, no click needed.
Pipeline
The automated assembly line your code travels through: build, test, deploy.
Why automate
Humans forget steps and make mistakes; automation does it identically every single time.
01

The pipeline

Continuous Integration merges and tests often. Continuous Delivery keeps main always shippable. Continuous Deployment ships every green build automatically.

Finished this topic?

Mark it done to earn 100 XP and keep your streak alive.