Apps & Software
What Is CI/CD and When Does a Development Team Need It
CI/CD is an automated flow that tests and releases every code change. This guide covers when a company or its vendor needs CI/CD, what changes in releases and their risk, and what to ask a vendor.
SEO and Content Specialist
7 min read
Short answer: CI/CD (continuous integration and continuous delivery or deployment) is a way of working in which every code change is merged as often as possible, tested automatically, and then prepared for release or released directly through the same flow every time. A company needs it when its application changes often, its releases involve several people, or a release has failed before and was hard to roll back. For an application released only a few times a year, the cost is often not yet worth it.
The question “what is CI/CD” usually comes up in a company at one of two moments: when an application vendor mentions it in a proposal, or when a release fails and nobody knows exactly which steps were run. For management, CI/CD is not about tools but about how safely and how quickly a change can reach users. This guide covers what it means, when it is worth setting up, how to measure it, and what to ask a vendor.
What is CI/CD: three terms that often get mixed up
CI/CD is a combination of three practices that follow one another. Martin Fowler defines continuous integration as a practice in which each team member merges their changes into the main codebase at least once a day, and each merge is verified by an automated build that runs the tests.
| Term | What it means | Release decision |
|---|---|---|
| Continuous integration (CI) | Code changes are merged often, then built and tested automatically | No release yet; what is protected is the integrity of the main code |
| Continuous delivery (CD) | Anything that passes the tests is always ready to release | Releasing to production becomes a business decision, run with a single step |
| Continuous deployment | Every change that passes the whole automated flow is released to production directly | No manual approval per release |
Most mid-sized companies only need to go as far as continuous delivery: testing and deployment run automatically, but a person still decides when a version goes to production. Continuous deployment demands very thorough automated tests, because there is no longer a human check before a change reaches users.
What changes in releases and their risk
Without CI/CD, a release is usually a set of manual steps that only one or two people know: copying files to the server, running database commands, then checking whether the application is still up. CI/CD turns those steps into a flow that is written as code and run the same way every time.
| Aspect | Manual release | With a CI/CD flow |
|---|---|---|
| Who can release | Whoever remembers the steps | Anyone on the team who is given the right |
| Testing | Depends on each person’s discipline | Runs automatically every time the code is updated |
| Size of changes | Piles up, released all at once | Small and frequent, easier to trace |
| Problematic release | Fixed in a panic | Rolled back to the previous version through a tested mechanism |
| Trail | Scattered across memories and chat messages | Recorded in the release flow’s history |
The risk that falls most visibly is dependence on a single person. A tidy release flow shows its value most when the person who usually runs it is away. The risk that does not go away: CI/CD only runs the tests that have been written. If the tests are thin, the automated flow only gets faulty code to users faster.
When does a development team need CI/CD
Not every team needs to set it up now. The following signs show that the cost is starting to be worth it:
- Frequent releases, for example several times a month or more, and the number is growing.
- Several developers or several vendors work on the same code, so changes often collide.
- A release has failed and took a long time to roll back.
- The test and production environments behave differently, so what passes in testing breaks in production.
- Only one person can release, and that person’s leave or replacement stops releases.
On the other hand, if the application rarely changes and is released a few times a year, the cost of setting up an automated flow is probably not yet worth it. In that case, documented release steps and a backup before each release are often enough. Projects built in stages with regular versions, as described in The Agile Method in Custom Application Projects, usually feel the benefit of CI/CD sooner because they release often.
How to measure the release flow before and after
Without numbers, it is hard to judge whether an investment in the release flow worked. The DORA (DevOps Research and Assessment) research program uses software delivery metrics that are now grouped into throughput and instability:
| DORA metric | Question it answers |
|---|---|
| Change lead time | How long a change takes from entering version control to running in production |
| Deployment frequency | How often releases to production happen |
| Failed deployment recovery time | How long it takes to recover from a failed release that needs immediate attention |
| Change fail rate | What percentage of releases need immediate attention, for example a rollback or hotfix |
| Deployment rework rate | What percentage of releases are unplanned and caused by an incident in production |
The first four metrics are the ones in use the longest, with names that have changed slightly over the years, while deployment rework rate was only added by DORA in 2024. What matters for management: record the numbers before the work starts, so the improvement can be proven, not just felt.
Security inside the release flow
A CI/CD flow holds access to the code and to the production servers, so it must be secured itself. NIST published SP 800-204D (February 2024), which specifically covers strategies for building software supply chain security into CI/CD flows. In practice, there are three things to ask about:
- Keys and secrets (database passwords, service tokens) are kept in a secrets manager, not written in the code or in configuration files stored in the repository.
- Vulnerability scanning of the code and third-party components runs as part of the flow, not as separate work after release.
- The right to run a release is controlled by role, and every release is recorded: who, when, and which version.
Questions for a vendor before the release flow is set up
- Where is the release flow configuration stored, and is it in a repository in our company’s name?
- Which tools are used, and can another party continue with them without a special license from the vendor?
- Which tests run automatically, and what is still tested manually?
- How is a version rolled back if a release goes wrong, and has the mechanism ever been tested?
- Which numbers are measured before and after the work?
- Who on our team will be trained to run releases, and when can our team release without help?
The first and second questions relate directly to ownership: a release flow that can only be run from the vendor’s account keeps you dependent, even if the source code already belongs to you. The clauses a contract should contain are covered in Source Code Ownership.
How Legia does it
In the DevOps & CI/CD service, Legia sets up a pipeline that runs testing and deployment automatically every time the code is updated, aligns the test and production environments, adds monitoring and alerts, and provides staged deployment with a rollback mechanism. Four numbers are measured before and after the work: release frequency, time from finished code to running on the server, recovery time after a problematic release, and release failure rate. The new flow runs alongside the old way until it proves stable, all configuration is stored as code in your repository using common, open tools, and the whole process from mapping to handover takes about 9 to 15 weeks. Other services in this pillar are on the Applications & Software page.
Frequently asked questions
Is CI/CD only for technology companies?
No. What decides it is how often the application changes and how much is at stake if a release fails, not the type of business. An internal application used every day by many employees can matter as much as a technology company’s product.
Do we need to go all the way to continuous deployment?
Not necessarily. Continuous delivery, where a version is always ready to release but release approval stays with a person, already delivers most of the benefit. Continuous deployment only makes sense once the automated tests are very thorough.
What is the difference between DevOps and CI/CD?
DevOps is a way of working that brings application development and operations together. CI/CD is one of the technical practices within it, namely the flow that carries code changes to the server. Monitoring, environment alignment, and rollback are also part of DevOps.
Can an existing application be given a CI/CD flow?
Yes, usually in stages. The first step that most often makes a difference is automated testing for the parts that break most often, plus aligning the environments, before the whole release is automated.

