Menu

Systems

Continuous Integration

Also known as: CI

Plain English

Regularly merging and testing code.

Definition

Continuous is the practice of frequently merging code changes into a shared repository with automated testing.

In practice

Ensures code is regularly tested and integrated to catch issues early.

In context

The practice is the frequency, not the tool. A team with a CI server that merges once a fortnight is running a , not continuous .

The reality

CI is often implemented but poorly maintained, reducing its effectiveness.

Compared with

Continuous Integration vs Continuous Delivery

CI merges and tests changes frequently so problems surface early. takes every passing to a state where it could be released. CI protects the codebase; CD shortens the path to users.

FAQ

Common questions

A few practical answers to the questions that usually come up around this term.

What is continuous integration?

It is merging code frequently with automated tests.

Why is CI important?

It catches issues early and improves quality.

What tools support CI?

Tools like GitHub Actions, Jenkins, and GitLab CI.

What is a common mistake?

Not maintaining tests or .

Related Services

Related Guides

Related Terms

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer