CI/CD
CI/CD is how you turn “it works on my machine” into repeatable, auditable change. These notes cover the decisions that keep pipelines fast and safe — not a museum of YAML that nobody dares to touch.
Topics
- What CI/CD is for
The job of the pipeline — fast feedback, reproducible artifacts, and controlled path to production.
- Continuous integration
Merge often, keep main green, and fail fast — the habits that make later delivery possible.
- Artifacts and versioning
Build once, promote the same bits — immutable artifacts, digests, and traceability from commit to runtime.
- Testing in the pipeline
What to automate where — unit, contract, integration, and e2e without making CI a overnight job.
- Delivery and promotion
Continuous delivery vs deployment — environments, approvals, and promoting the same artifact safely.
- Progressive delivery
Rolling, canary, and blue/green — limiting blast radius when the pipeline says go.
- Pipeline security
Secrets, runners, supply chain, and least privilege — hardening CI/CD so the pipeline is not the weakest door.
- Operating pipelines
Speed, ownership, templates, and metrics — keeping CI/CD useful after the first green build.