Back to library

⛓️CI/CD Pipeline Fundamentals

Build a working mental model of CI/CD -- stages, gates, artifacts, environments, rollbacks -- then wire up a real GitHub Actions pipeline and design one for a multi-env deploy you actually own.

Foundations14 drops~2-week path · 5–8 min/daytechnology

Phase 1The Mental Model of a Pipeline

See why pipelines exist and how the stages compose

4 drops
  1. CI/CD is a feedback loop, not a deploy button

    6 min

    CI/CD is a feedback loop, not a deploy button

  2. Build, test, package, deploy -- in that order, every time

    6 min

    Build, test, package, deploy -- in that order, every time

  3. Pipelines run on events, not on schedules

    6 min

    Pipelines run on events, not on schedules

  4. A gate is a contract, not a checkbox

    7 min

    A gate is a contract, not a checkbox

Phase 2Wiring Your First Real Pipeline

Wire a real GitHub Actions pipeline end to end

5 drops
  1. A workflow is just events, jobs, and steps

    6 min

    A workflow is just events, jobs, and steps

  2. Build is the first promise your pipeline makes

    7 min

    Build is the first promise your pipeline makes

  3. Tests are the loudest signal in your pipeline

    7 min

    Tests are the loudest signal in your pipeline

  4. Secrets aren't config -- they need their own home

    7 min

    Secrets aren't config -- they need their own home

  5. Cache the boring parts so the interesting parts run fast

    7 min

    Cache the boring parts so the interesting parts run fast

Phase 3Tests, Artifacts, Environments, Rollbacks

Connect tests, artifacts, environments, and rollbacks

4 drops
  1. Build once, deploy many -- the same artifact, every environment

    7 min

    Build once, deploy many -- the same artifact, every environment

  2. Same code, different config -- never the other way around

    7 min

    Same code, different config -- never the other way around

  3. Deploys are not events -- they're transitions you can pause

    8 min

    Deploys are not events -- they're transitions you can pause

  4. If you can't roll back in 60 seconds, you don't have rollbacks

    8 min

    If you can't roll back in 60 seconds, you don't have rollbacks

Phase 4Design a Multi-Env Deploy Pipeline

Design a pipeline for a real multi-env deploy

1 drop
  1. Design the pipeline you'd actually trust

    8 min

    Design the pipeline you'd actually trust

Frequently asked questions

What's the difference between continuous integration and continuous delivery?
This is covered in the “CI/CD Pipeline Fundamentals” learning path. Start with daily 5-minute micro-lessons that build from fundamentals to hands-on application.
Why does my CI pass but production still breaks?
This is covered in the “CI/CD Pipeline Fundamentals” learning path. Start with daily 5-minute micro-lessons that build from fundamentals to hands-on application.
How do I roll back a deploy without rebuilding?
This is covered in the “CI/CD Pipeline Fundamentals” learning path. Start with daily 5-minute micro-lessons that build from fundamentals to hands-on application.
When should I split staging and production environments?
This is covered in the “CI/CD Pipeline Fundamentals” learning path. Start with daily 5-minute micro-lessons that build from fundamentals to hands-on application.
What's the difference between an artifact and a build?
This is covered in the “CI/CD Pipeline Fundamentals” learning path. Start with daily 5-minute micro-lessons that build from fundamentals to hands-on application.