World map

 

BM

World 7: Robots: Actions & CI/CD

What CI/CD means

You will learn: how a robot can test and ship your code on every push.

The problem

Friday night. Mei merges a change. The diary site breaks. Nobody ran the tests. Who should run them, every single time?

Watch

Tap each point on the timeline.

Tap each step. This robot habit is continuous integration (CI): A robot tests every change as soon as you push it., or CI. Every push gets checked, so bugs show up early.

Watch

Practice repo — not a real website
aina-codes / diary
CI and deploy #41
Passed push on main
Tap a step to see its log.
test
deploy

Tests passed? Then a robot can ship it too. That is continuous delivery / deployment (CD): A robot ships your tested changes, so users get them fast., continuous delivery or deployment. Tap a step to peek at its log.

Try it

Is it checking, or shipping? Sort each job.

Drag a card into a box. Or tap the card, then tap the box.

      Watch

      bash
      ls .github/workflows
      ci.yml deploy.yml

      GitHub’s robot is called GitHub Actions: GitHub's robot service. It runs your workflows on its computers.. You write its instructions in files. They live in .github/workflows/ inside your repo.

      Predict

      Mei’s next push breaks a test. What does CI do?

      Check

      Good habit, or needs work? Swipe each one.

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 4

      Push small changes often, so CI checks each one

      You did it!

      You can now explain CI and CD.

      Go deeper (optional)

      CD comes in two flavours. Continuous delivery: every change is ready, and a person presses ship. Continuous deployment: it ships by itself when the checks pass. Many tools do CI. This world uses GitHub Actions.