World map

 

BM

World C1: Pipeline Thinking

Same ideas in GitLab, Jenkins, Azure

You will learn: how your pipeline ideas carry over to GitLab CI, Jenkins and Azure Pipelines.

Checked with GitHub Actions 2026-10 on 31 Oct 2026

The problem

Your new job uses GitLab, not GitHub. Do you start from zero?

Watch

Tap the one that is not YAML.

0 of 1 found

Four tools, one station: run the tests. Only the words change.

Watch

Tap each point on the timeline.

Tap each GitHub word to see its twins. The worker machine is often called an agent: Jenkins and Azure Pipelines call the worker machine an agent. GitHub and GitLab call it a runner..

Try it

Which tool does each clue belong to?

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

        Predict

        In GitLab, every job in the test stage passes. What runs next?

        Try it

        Here is a GitLab job. Build the same job in GitHub Actions.

        test:
  image: node:24
  script:
    - npm ci
    - npm test

        Tap blocks to add them. Put them in order.

        Blocks

        Your workflow

        Tap a block above to start.

        Workflow file .github/workflows/

        name: CI

        What runs

        Nothing to run yet.

        You did it!

        You can now read a pipeline in GitLab, Jenkins or Azure Pipelines.

        Go deeper (optional)

        Where the story breaks: a real belt carries one dish at a time. A pipeline can run many jobs side by side. And copying a build is free, so one pack can go many places.

        Jenkins usually runs on your team’s own servers.

        Real rep (optional): open a public GitLab project. Find its .gitlab-ci.yml and name its stages.