cicd
Installation
SKILL.md
CI/CD Pipeline Patterns and Deployment Strategies
Continuous Integration, Continuous Delivery, and Continuous Deployment form a spectrum of automation practices. Each builds on the previous one, progressively reducing manual intervention between a code change and its availability to users.
CI vs CD vs CD
| Practice | What It Automates | Gate to Next Stage |
|---|---|---|
| Continuous Integration | Merging, building, and testing code on every commit | Automated tests must pass before merge |
| Continuous Delivery | Packaging and promoting artifacts through environments | Manual approval before production deployment |
| Continuous Deployment | Full path from commit to production without manual steps | Automated quality gates replace human approval |
Continuous Integration is the foundation. Without reliable, fast integration, neither delivery nor deployment is sustainable. Start here and expand outward.
Pipeline Design Principles
A well-designed pipeline gives developers fast, trustworthy feedback while preventing broken code from reaching users.