What is CI/CD (Continuous Integration/Delivery)

Definition

CI/CD (Continuous Integration and Continuous Delivery/Deployment) is the practice of automatically building, testing, and releasing code changes through a pipeline, so that integrating and shipping small changes frequently becomes fast, reliable, and low-risk.

« Back to Glossary Index

Integrates and tests every change automatically, catching issues immediately
Enables frequent, small releases that are lower-risk than big-bang deployments
Automates the path from commit to deployment, removing manual error
Speeds delivery while improving confidence through consistent testing

Real World Example

A development team uses a CI/CD pipeline that builds, runs tests, and deploys to staging on every commit, so a feature can move from code to production in hours with automated checks guarding each step.

FAQs

What is the difference between continuous delivery and deployment?

Continuous delivery automates everything up to a release-ready state requiring manual approval to ship, while continuous deployment releases automatically.

What does continuous integration solve?

It catches integration problems early by automatically building and testing every change as it merges, rather than late in a big merge.

Why is CI/CD valuable?

It makes releasing software fast, frequent, and reliable, reducing risk and accelerating feedback.