CI/CD CI/CD

CI/CD is an automatic path that tests every change to your software and puts it live once the tests pass, so a release stops being an event people dread.

Also known as continuous integration continuous delivery deployment pipeline

Definition

CI/CD moves a change in your software from the person who wrote it to the people who use it, without anyone doing the steps by hand. The name has two halves. Continuous integration means every small change joins the main copy of the code the same day, so a machine can test it straight away. Continuous delivery means that once those tests pass, the change goes live, or becomes ready to go live at the press of one button.

Most businesses have lived the other version, where someone stays up late on a Thursday and works down a printed checklist. That person copies files onto a server and hopes, which is nervous work, so it gets done rarely. And because it is done rarely, each release carries three months of changes at once. So when something breaks on Friday morning, nobody can say which of the forty changes did it.

Here is the part people get wrong, because most of the gain does not come from the automation itself. It comes from how often you can release once the automation exists. A release holding one change is easy to check and easy to undo, while a release holding forty is a mystery with a deadline attached. That is why teams shipping every day have fewer bad nights than teams shipping every three months. The difference is the size of the step, not the cleverness of the tool.

That automatic route, which people call the pipeline, is also the natural home for the checks nobody remembers to run by hand. Tests come first, but so does a scan for known holes in the outside code your system leans on. Linkysoft builds that scan into the pipeline on every web application project, because a check that runs when someone remembers is a check that does not run. Our cybersecurity team then decides what the pipeline refuses to release.

There is one honest limit. A mobile app cannot go live in four minutes, because Apple and Google review each new version first, and that takes hours or days. The pipeline still builds and tests the app, and only the last step waits. Before you sign anything, ask your supplier to release a version in front of you and then undo it while you watch. Linkysoft answers that with a demonstration rather than a document, because how long the undo takes tells you more than any diagram.

Questions about CI/CD

Do I need CI/CD for a small project?
If your system changes a few times a year, it is not the first thing to spend on. If it changes every week, the pipeline pays for itself in about a month of saved evenings.
Does CI/CD mean changes go live without anyone checking them?
No. A person still reads the change and approves it. The pipeline only takes over the steps a machine can check, such as running the tests and copying the files.
How long should a release take?
For a web system, minutes. A phone app is different, because Apple and Google review each version first, so plan on hours or a couple of days.
What happens when a release breaks something?
You put the previous version back, usually in one step. Ask your supplier to show that step working rather than describe it, because a rollback nobody has practised rarely works on the bad day.
Is CI/CD the same as DevOps?
No. DevOps is a way of working where the people who build the software also look after it while it runs. CI/CD is one practical piece of that, and the easiest piece to see.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.