---
title: "CI/CD"
description: "CI/CD automates building, testing and deploying code. Learn how continuous integration differs from continuous delivery and where these pipelines are used."
url: "https://nodea.io/en/glossary/ci-cd"
lang: "en"
updated: "2026-07-13"
---

# CI/CD

> CI/CD is a set of practices that automate integrating, testing and deploying code, shortening delivery time while reducing the risk of shipping bugs.

**CI/CD** is a set of software engineering practices that automate integrating code changes, testing them and shipping them to a server. The acronym combines two ideas: *Continuous Integration* and *Continuous Delivery/Deployment*. The goal of CI/CD is to shrink the gap between writing code and running it in front of users, while lowering the risk of defects reaching production.

## How CI/CD works

At its core is a **pipeline** — a defined sequence of steps triggered automatically after each change in a [repository](https://nodea.io/en/glossary/repository). During continuous integration the system checks out the code, builds the application and runs a suite of checks: [unit tests](https://nodea.io/en/glossary/unit-testing), integration tests and quality gates. If any step fails, the pipeline stops and the team is notified immediately.

The continuous delivery stage packages a release-ready artifact, while continuous deployment goes further and pushes the new version to production without manual intervention. The whole process often relies on containerization with [Docker](https://nodea.io/en/glossary/docker), which guarantees identical runtime conditions at every stage.

## Practical applications

CI/CD is used wherever fast and safe delivery matters: web applications, microservices, e-commerce platforms and SaaS products. A typical pipeline might build an image, run database migrations, execute tests and deploy the result to a production server.

- **Faster releases** — instead of rare, large rollouts, teams ship small changes many times a day.
- **Fewer bugs** — automated tests catch regressions before they reach users.
- **Repeatability** — every deployment follows the same proven procedure.

Running CI/CD pipelines requires a stable server environment — a [VPS](https://nodea.io/en/glossary/vps) or dedicated server works well for hosting a runner and test environments. CI/CD is now a cornerstone of [DevOps](https://nodea.io/en/glossary/devops) culture and modern software delivery.

### How does CI differ from CD?

CI (Continuous Integration) automates merging and testing code in a repository. CD covers Continuous Delivery, which prepares a release-ready artifact, or Continuous Deployment, which automatically pushes it to production.

### Do I need special tools for CI/CD?

Yes. You need an automation server such as GitLab CI, GitHub Actions or Jenkins. These run a pipeline on a server or container every time the code repository changes.

## Related

- [DevOps](https://nodea.io/en/glossary/devops)
- [Git](https://nodea.io/en/glossary/git)
- [Docker](https://nodea.io/en/glossary/docker)
- [Deploy](https://nodea.io/en/glossary/deployment)
- [Kubernetes](https://nodea.io/en/glossary/kubernetes)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/ci-cd.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)