CI/CD

in English: continuous integration / continuous delivery (or continuous deployment)

advancedwidespread

An automated assembly line that immediately builds, tests, and brings every code modification to a release-ready state, or even deploys it.

In plain terms

Imagine a production line in a large bakery: the baker only puts in the dough, and the conveyor belt automatically carries it to the oven, then to quality control and packaging. CI/CD is the same for software: the developer uploads their modification, and from then on machines handle the testing and deployment.

CI (Continuous Integration) means that team members frequently – typically at least once a day – merge their work into a shared code repository, and automatic tests run after each merge. Thus, errors are usually discovered within minutes, not weeks later when no one remembers what caused them.

CD is the second half of the pipeline and can mean two things. In continuous delivery, tested software automatically assembles into a deployable package and reaches users after human approval. In continuous deployment, the release happens without human intervention.

In the past, releasing a new version was a rare, long, and nerve-wracking event. With CI/CD, release becomes routine: it happens in small steps, frequently, and if something goes wrong, rolling back is easier.

How it works

The developer (or a coding agent) uploads the modification to the shared code repository, which automatically triggers the process.
A server builds the running program from the latest code; if this fails, the process stops, and the author receives an immediate notification.
Automatic tests and checks run: do the functions work, are there known security vulnerabilities, and does the code comply with the team's rules?
If everything is green, the program assembles into an installable package and moves to a test environment where it can be trialed under realistic conditions.
The final step is rollout: either approved by a human or fully automated, often gradually, initially for only a small portion of users.

An everyday example

Your banking app on your phone updates regularly, perhaps every few weeks, while the bank's backend systems update even more frequently, mostly without downtime. This is underpinned by CI/CD: every small fix passes through a long series of automated tests before reaching you.

Who is affected

developerPart of your daily work: this assembly line checks every modification you upload and signals back if you made a mistake. → Code

entrepreneur, executiveThis determines whether your company's software receives new features or bug fixes in hours instead of weeks, and how much risk a release carries.

jobseeker, new graduateIt appears in many developer and operations job postings, so it is worth knowing at least the basics. → Work & HR

everyoneThis is why your applications often update frequently, invisibly, and mostly without downtime.

A common misconception

MythIf there is CI/CD, the program is definitely bug-free because the machine checks everything.

In realityThe pipeline only checks what tests have been written for. If the tests are incomplete or flawed, buggy code reaches users as quickly as good code.

Limits and risks

It is worth as much as the tests behind it: weak tests create a false sense of security.
The assembly line is a sensitive target: it accesses passwords and live systems, so if breached, an attacker can tamper with released software.
Its deployment and maintenance require time and expertise; for small projects, the investment pays back slowly.
If AI agents write the code, the number of changes spikes, and the pipeline becomes one of the last lines of defense; without human review, this is risky.

Similar, but not the same

DevOps – DevOps is the philosophy and culture of collaboration between development and operations, while CI/CD is one of its specific tools.
continuous deployment – In continuous delivery, deployment is still approved by a human, while in continuous deployment this step is fully automatic.
Version control – A version control system (such as Git) stores and tracks code changes, while CI/CD builds, tests, and releases the program in response to these changes.

Related concepts

Broader

DevOps, Software development, Automation

Narrower

continuous integration, Continuous delivery, Continuous deployment, automated testing

On the edge

Version control, Git, coding agent, Code repository, MLOps

A brief history

The earliest known mention of the term 'continuous integration' is attributed to Grady Booch, who used it in his 1994 book. In the late 1990s, the extreme programming (XP) movement associated with Kent Beck made it a daily practice. The concept of continuous delivery was popularized by Jez Humble and David Farley in their 2010 book, 'Continuous Delivery'.

Where things stand

As of late 2026, CI/CD is standard equipment in professional software development, and the major code-hosting providers offer it built in. What is new is that more and more changes are submitted by coding agents, so the pipeline's checking role has become even more important.

Status: 2026 November

In the news

Appears in 3 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Anthropic describes how agentic coding strains CI and how it scaled test impact analysisSep 14, 2026 · Code
Claude Code vulnerabilities: CI/CD leak, auto mode bypassed, AWS credential theftSep 7, 2026 · Code
JetBrains renews TeamCity with AI and MCP supportSep 7, 2026 · Code

Also known as

CI/CD · CICD · CI/CD pipeline · continuous integration · continuous delivery · continuous deployment · continuous deployment · build pipeline

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.