Continuous Integration & Continuous Delivery (CI/CD) Definition
CI/CD stands for continuous integration and continuous delivery, a set of DevOps practices that automate how software is built, tested, and released. Continuous integration (CI) means developers merge their code changes into a shared repository frequently, where each change automatically triggers a build and a suite of tests to catch problems early. Continuous delivery (CD) extends that by automatically preparing every validated change for release, so code is always in a deployable state.
Together these practices form a CI/CD pipeline: an automated workflow that carries code from commit through build, test, and deployment with minimal manual intervention. The goal is to release software faster, more frequently, and with fewer defects by removing the slow, error-prone handoffs of traditional release cycles.
Continuous delivery automates everything up to release but keeps a manual approval step before production, while continuous deployment goes one step further and pushes every passing change to production automatically.
What is a CI/CD pipeline?
A CI/CD pipeline is the automated workflow that moves code from a developer's commit through to production. It runs in defined stages: source (a change is pushed to the repository, triggering the pipeline), build (the code is compiled and dependencies are resolved), test (automated unit, integration, and security tests validate the change), and deploy (the validated build is released to staging or production). If any stage fails, the pipeline stops and alerts the team, so broken code never reaches users. Each commit runs through the same consistent path, which removes manual handoffs and makes releases repeatable and predictable.
What is the difference between continuous delivery and continuous deployment?
Both start the same way, every code change is automatically built, tested, and prepared for release, but they differ at the final step. Continuous delivery keeps a manual approval gate before production: the code is always deployable, but a human decides when to ship it. Continuous deployment removes that gate entirely, automatically pushing every change that passes testing straight to production, with no human intervention. This is why "CD" is ambiguous in CI/CD: it can mean either, and which one a team practices depends on their risk tolerance, regulatory requirements, and confidence in their automated test coverage.
What are CI/CD tools?
CI/CD tools are the software platforms that automate the pipeline, orchestrating builds, running tests, and handling deployments whenever code changes. Widely used options include Jenkins (an open-source automation server and one of the longest-established), GitLab CI/CD and GitHub Actions (built directly into their source control platforms), CircleCI and Travis CI (cloud-native CI services), and Argo CD (for Kubernetes deployments). Most integrate with version control, container registries, testing frameworks, and security scanners. The right choice depends on your existing stack, whether you need self-hosted or cloud-managed infrastructure, and how complex your deployment targets are.