CI/CD: automatic quality gates and releases you can repeat

How to set up integration and release pipelines: automatic checks on every change, tests in the pipeline, secrets, gradual release strategies and rollback.

MethodologymetodologiaCI/CDautomazioneingegneria del software19 November 2026 · 3 min read

A release done by hand, following a list kept in someone's head, works as long as the person doing it is the one who knows it. At the first absence, the first skipped step, the release becomes a risky event. Delivery automation (CI/CD) turns that list into a sequence that runs the same way every time.

Quality gates

The continuous integration (CI) pipeline runs a series of checks on every change, in order from the fastest to the slowest, and stops at the first one that fails. The typical gates:

  1. Build. The project builds.
  2. Static checks. Formatting, style rules, types.
  3. Automated tests. Unit, then integration.
  4. Security checks. Dependencies with known vulnerabilities, secrets in the code.
  5. Optional extra checks. Performance, accessibility, full tests.

A change enters the main branch only if all the gates are green. The aim is not bureaucracy: it is that nobody has to remember to run the checks.

A fast pipeline

If the pipeline takes half an hour, people stop waiting for it and work around it. Keep the quick checks first, run in parallel where you can, cache dependencies already downloaded. An unstable test (one that sometimes passes and sometimes does not) must be fixed or isolated at once: it teaches people to ignore red.

Secrets and environments

Secrets are not in the repository or in the pipeline files: they live in the platform's secret manager, with access limited per environment. Each environment (development, test, production) has its own configuration, and the production one is not accessible to those who should not have it.

Release strategies

The release (CD) can be:

  • Direct, for simple, low-risk systems.
  • Gradual: a share of users gets the change, and you watch before widening it.
  • With feature flags: the code is released but the feature is switched on later.
  • With parallel environments, to swap versions and go back in a few seconds.

The choice depends on the cost of a mistake and the ability to notice it early.

Rollback is part of the release

Before releasing you know how to undo: which version to restore, who decides, how long it takes. A release without a rehearsed rollback is not a process, it is a bet. Where there are data migrations, you decide beforehand whether they can be undone.

Warning signs

  • Manual releases with steps kept from memory.
  • Changes that get in without passing the pipeline.
  • Unstable tests tolerated.
  • Secrets in the pipeline files.
  • A slow pipeline that people work around.
  • No rollback plan.
  • Releasing at the end of the day or on a Friday with no cover.

An example

A team releases every two weeks with a list of fourteen manual steps. Once one is skipped (the data migration) and the service is down for an hour. After automating the sequence, the steps are the same but the pipeline runs them, and the migration can no longer be forgotten.

When to use it

When setting up or changing a build and release pipeline, when you need automatic quality gates, tests configured in CI, or release strategies.

This method derives from the open-source agent-skills family by Addy Osmani (MIT licence), rewritten and adapted.

This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

ci-cd-and-automationA method for setting up integration and release pipelines: quality gates in order of speed, a fast pipeline, handling of secrets and environments, gradual release strategies, a planned rollback. Use it when creating or changing a CI/CD pipeline.