Course outline · 0% complete

0/29 lessons0%

Course overview →

From CI to CD: the pipeline

lesson 8-1 · ~10 min · 22/29

Quiz

Warm-up from unit 7: after your CI passes on a commit to main, what exists that didn't before?

CD: the next two letters

CI stops at "the code is tested". CD continues to "the code is running for users". Two meanings, and interviewers love the distinction:

  • Continuous delivery: every commit that passes CI is automatically packaged and ready to deploy, but a human presses the deploy button
  • Continuous deployment: no button. Passing main goes straight to production, minutes after merge

Either way, the full pipeline is one automated lane:

commit → test → build image → push to registry → deploy

Each stage only runs if the previous one succeeded (exit codes, lesson 7-1). The image that reaches production is the exact same bytes that passed the tests, because images are immutable (lesson 1-2) and the registry (lesson 6-1) is the hand-off point between CI and the servers.

committestbuildpushdeployone commit rides the whole pipeline, stopping at the first red stage
A commit riding the CD pipeline. Every stage gates the next, and the image that deploys is byte-for-byte the one that passed the tests.

Quiz

Your team auto-packages every green commit but a release manager clicks deploy each Thursday. Which practice is that?

Problem

Fill the blank with one word: in continuous __________, a passing commit reaches production with no human approval step at all.