← Back to trackModule: Pipeline Foundations

INTERMEDIATE · Easy · 35m

What CI/CD really automates

CI/CD: Starter to Shipping

Lesson notes

Goal

Understand what CI/CD automates and how it reduces risk in shipping software.

The delivery pipeline (simple)

Commit -> Build -> Test -> Package -> Deploy -> Verify -> Monitor

CI/CD is not a tool. It is a set of automated checks + repeatable steps.

CI (Continuous Integration)

Focus: integrating code changes safely. Typical automation:

  • install dependencies
  • build
  • unit tests
  • lint/typecheck

CD (Continuous Delivery / Deployment)

Focus: releasing reliably. Typical automation:

  • create artifact (Docker image)
  • deploy to staging
  • run integration tests
  • optional approval
  • deploy to production (delivery) or auto deploy (deployment)

What to automate first

  1. Build + unit tests (fast feedback)
  2. Lint/typecheck (cheap)
  3. Packaging (reproducible artifacts)
  4. Deploy to staging
  5. Production deploy with guardrails

Exercises

  1. Write down your current manual release steps.
  2. Convert them into a pipeline stage list.
  3. Mark which steps can be automated today.

Next Step

Design a pipeline that is fast, reliable, and easy to debug.

View full outline

Outline

Use the outline to jump to any topic.

Track tools

Search lessons, continue where you left off, and track completion.

Modules

3

Lessons

6

Estimated Time

340m

Completion

0%

0/6 lessons

Your progress: 0%

Complete a lesson to increase progress

Outline

Open a lesson for full notes. Mark completed to update your progress.

Goal: Understand what CI/CD automates and how it reduces risk in shipping software. The delivery pipeline (simple) CI/CD is not a tool. It is a set of automated checks + repeatable steps. CI (Continuous Integration) Focu…

Goal: Build pipelines that developers trust: fast feedback and stable results. Key principles fail fast (lint/unit tests early) deterministic builds (pin versions) cache smart (dependencies) keep stages small and clear a…

Goal: Create a workflow that is secure, repeatable, and deploy ready. A clean workflow structure Keep CI separate from deploy if possible. Key things to get right least privilege permissions secrets from GitHub Secrets (…

Goal: Find root causes fast when CI/CD fails. Debug checklist 1. Which step failed? 2. Is it deterministic or flaky? 3. Did dependencies change? 4. Is the environment different from local? 5. Does it fail only on main? T…

Goal: Build reproducible Docker images and tag them in a way that supports rollbacks. Multi stage builds (why) smaller final image faster builds fewer runtime dependencies Tagging strategy (simple and effective) Use: imm…

Goal: Release changes without taking production down. Patterns Rolling Update instances gradually. Simple, but can still cause partial outages. Blue/Green Two environments: blue = current green = new Switch traffic when…