Course
CI/CD: Pipelines That Earn Trust
Continuous integration and delivery the way senior teams run it: fast feedback loops, test gates that mean something, cached builds, deployment strategies, and rollbacks that aren't a plan-B panic.
CI Fundamentals
Why the loop exists, what belongs in it, and the speed budget that keeps it used.
The Pipeline
GitHub Actions anatomy, caching, matrices — turning a YAML file into a trustworthy gate.
- 01GitHub Actions Anatomy: Events, Jobs, RunnersThe three-level model — workflow triggers, parallel jobs, sequential steps — and the YAML structure behind every CI file you've seen.22mOpen
- 02Test Gates and Caching: Fast Without Cutting CornersSplit jobs for parallelism, cache dependencies correctly, and keep the suite honest under pressure.22mMembers
- 03Matrices and Monorepos: Scaling the PipelineTesting across versions with matrix, and running only what changed with paths filters — CI that scales with the codebase.20mMembers
CD & Releases
Deploy strategies, secrets in CI, and rollbacks as a designed feature rather than a hope.
- 01Deployment Strategies: Rolling, Blue-Green, CanaryHow the new version reaches users — the three deployment shapes and when each one earns its complexity.22mMembers
- 02Secrets in CI: Not in the Code, Not in the LogsGitHub Secrets vs env vars vs OIDC — where credentials live, why they leak, and the OIDC pattern that removes them.20mMembers
- 03Rollback and Recovery: The Rehearsed EscapeRollback as a feature you test, not a panic you improvise — artifacts, database safety, and the on-call muscle.20mMembers