CI/CD
CI/CD Pipeline
CI/CDAn automated sequence that tests, builds, and deploys code every time it changes.
Reviewed by the RadarTrek editorial team · June 2026
A CI/CD pipeline runs automatically on every push or pull request: continuous integration (CI) runs tests and catches breakage immediately, and continuous deployment/delivery (CD) automates getting that tested code into production. The point is removing manual, error-prone steps from the path between "code is written" and "code is live."
Why it matters
- —CI catches a broken build within minutes of a push, instead of someone discovering it days later in production.
- —A pipeline that requires a human to manually run tests before merging isn't really CI — automation is the whole point.
- —Preview deployments (a live URL per pull request) let reviewers see a change running, not just read a diff.
Where to learn this
🎓
How CI/CD Works
CI/CD with GitHub Actions course
This is the exact lesson that covers this term in depth — with examples, diagrams, and a hands-on exercise.