What is CI/CD?
Continuous Integration, Delivery, and Deployment — the philosophy and the pipeline
Skills taught: cicd.ci-vs-cd, cicd.pipeline-stages, cicd.devops-culture
The 'works on my machine' problem — at scale
In the early 2000s, software teams integrated code once every few weeks — or months. Every integration was a painful, risky event: merge conflicts piled up, tests hadn't run in weeks, and the release process involved days of manual steps. Bugs that could have been caught in minutes festered for weeks. CI/CD was invented to solve this: make integration frequent, make testing automatic, and make deployment a non-event.
CI, CD (Delivery), CD (Deployment) — the three terms
- Continuous Integration (CI)
- Every code push automatically triggers: build the project, run all tests, check code quality. If anything fails, the developer is notified immediately — while the context is fresh. Goal: always keep the main branch in a deployable state.
- Continuous Delivery (CD)
- After CI passes, the code is automatically packaged and deployed to a staging environment, ready for production at the push of a button. The deployment to production is a manual trigger — but the process is fully automated.
- Continuous Deployment (CD)
- Goes one step further: if all checks pass, code is deployed to production automatically — no human in the loop. This is what companies like Netflix, Etsy, and Shopify do — deploying hundreds of times per day.
Why CI/CD changes how teams work
- Smaller, safer changes — when deploying is easy, you deploy often. Small changes are easier to review, test, and roll back.
- Faster feedback — a bug caught in CI minutes after push is 10× cheaper to fix than one found in production weeks later.
- No 'integration hell' — merging frequently means conflicts are small and frequent instead of large and catastrophic.
- Confidence — developers can refactor fearlessly when tests run automatically on every push.
Frequently Asked Questions
Do I need CI/CD for my personal project?
Yes — even a simple GitHub Actions workflow that runs tests and deploys on push saves time and prevents embarrassing bugs from reaching production. The setup takes 30 minutes and pays back immediately. Even a one-person project benefits from 'the tests passed' confidence before every deploy.