Pipelines as code & quality gates
P36.pipelines-as-code.01 · Audience: guest, it-ml, language-pro
Once a project is packaged, the next question is: what stops broken code from shipping? A CI pipeline — declared as code, run on every push, enforced as the gate on a merge. This module has you write a real GitHub Actions workflow and run it through a CI simulator, so the mechanics — gate ordering and fail-fast — are yours.
ⓘ Concept: A workflow is data the runner executes
needs (its gate) and the steps it runs. You declare the what; the runner works out the order. Because it's a file in the repo, it's reviewed like any change — and the same checks run locally and in CI.Why it matters — A pipeline that lives in the repo is versioned and reviewed like code — one source of truth for what 'good' means, not steps clicked together in a UI.
This repo's own workflow gates every change with one make quality job — the
pipeline that gated this very lesson:
name: vnext-ci
on: [push, pull_request]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- run: make quality
Ask the mentor about this module
Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.
🎓 Practice ladder
2 graded rungs · ~26 minAuthor a real Actions workflow and run it through the CI simulator, then design a pipeline in an interview-style prompt.
Rung 1 — a pipeline as code (real YAML, simulated run)
Loading exercise…
Rung 2 — CI pipelines & quality gates (interview)
Loading exercise…
One pipeline, one environment — so far. The next module fans it out across a matrix of versions and platforms, and decides which build actually ships.
Where next?
Later in Pipelines as Code & Quality Gates
This module unlocks