Continuous Integration and Continuous Delivery/Deployment: automatically building, testing, and shipping code on every change, so integration problems surface in minutes instead of at a painful merge weeks later. Part of the DevOps curriculum.
~9,000 words across 12 notes. This section was a 142-line stub until August 2026, while 2,776 lines of GitHub Actions material sat in git/ — the wrong folder, since Actions is CI/CD rather than version control. That material was moved here and split into notes 03–12; git/ keeps version control.
Grounding: this vault deploys itself via a GitHub Actions workflow (.github/workflows/deploy.yml), which note 02 dissects line by line. Notes 03–12 come from real pipeline work on production deployments. The competing-tools comparison in note 02 is [reference].
Reading order
The model
- CI/CD Concepts — [Intermediate] — CI vs CD vs continuous deployment, the anatomy of a pipeline (stages, gates, artifacts), and the principles that make it work. Vendor-neutral
- CI/CD Tools — [Intermediate → Advanced] — GitHub Actions dissected via this vault’s own deploy pipeline, plus the Jenkins / GitLab CI / CircleCI landscape
GitHub Actions in depth
- Fundamentals — [Intermediate] — workflow → job → step → action, where files live, the execution flow, and the complete top-level YAML including concurrency and permissions
- Triggers, Jobs and Runners — [Intermediate] —
on:in full, job and step structure,runvsuses, outputs, fan-out/fan-in, and the machines it all runs on - Contexts, Secrets and Environments — [Intermediate] — the context objects, expression functions, and how secrets and environments are scoped
- Caching, Artifacts and Matrix Builds — [Intermediate] — the three things that make a pipeline fast and broad
- Reusable Workflows and Composite Actions — [Intermediate → Advanced] — how to stop copy-pasting YAML across repos
Building real pipelines
- CI Pipelines — [Intermediate] — a complete build, worked through in Node/NestJS and Java/Spring Boot
- CD, Deployment Strategies and Releases — [Intermediate → Advanced] — deploy structure and rollback, recreate/rolling/blue-green/canary in depth, and automated releases
- Securing the Pipeline — [Intermediate → Advanced] — your CI system holds production credentials and runs third-party code. Least privilege, OIDC, dependency scanning, supply-chain hardening
- Real-World Pipelines, End to End — [Advanced] — two complete production pipelines, top to bottom
- Troubleshooting Workflows — [Reference] — debug logging, tmate SSH into a runner, the errors you’ll actually hit
Where this borders other domains
CI/CD sits between several things and it’s easy to duplicate them here. Deliberately kept elsewhere:
- Branching strategies, branch protection, PR practice, semantic versioning → the git course. A pipeline enforces these rules; it doesn’t define them. Specifically 13-branching-strategies and 14-github-and-ci
- The deploy targets → Docker, Orchestration, VPS
- What the deploy stage invokes → Infrastructure as Code
- The pull-based alternative → GitOps, where the cluster reconciles itself from git instead of CI pushing to it
Related
- DevOps curriculum map
- Git course — version control, the roadmap’s VCS pillar
- Testing (Java) — the test gates a CI pipeline enforces
- Observability — how you know a deploy went well
Software engineering
Infrastructure & security
Computer science
Hardware & engineering