Do you have a Continuous Integration (CI) Server?

Last updated by Brady Stroud [SSW] about 1 month ago.See history

A Continuous Integration (CI) server monitors the Source Control repository and, when something changes, it will checkout, build and test the software.

If something goes wrong, notifications are sent out immediately (e.g. via email or Teams) so that the problems can be quickly remedied.

It's all about managing the risk of change

Building and testing the software on each change made to the code helps to reduce the risk of introducing unwanted changes in its functionality without us realising.

The various levels of automated testing that may form part of the CI pipeline (e.g. unit, contract, integration, API, end-to-end) all act as change detectors, so we're alerted to unexpected changes almost as soon as the code that created them is committed to the code repository.

The small change deltas between builds in combination with continuous testing should result in a stable and "known good" state of the codebase at all times.

Tip: Azure DevOps and GitHub both provide online build agents with a free tier to get you started.

Adam Cogan
Brendan Richards
Matt Wicks
We open source. Powered by GitHub