---
title: "CI/CD pipelines | Skills We Assign For | Azendo"
description: "CI/CD pipelines — speed, trust, deployment frequency, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/ci-cd-pipelines/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# CI/CD pipelines.

A CI/CD pipeline automates the path from commit to production: building, testing, checking quality gates and deploying, so releasing is a routine automated event rather than a manual procedure.

## Where CI/CD pipelines fits on a long engagement.

Pipeline speed shapes behaviour more than any policy. A pipeline returning in five minutes means small frequent changes; one taking forty means batched changes, which are harder to diagnose when something breaks and riskier to deploy.

Trust matters as much as speed. A pipeline with intermittently failing tests trains the team to rerun rather than investigate, and once that habit exists a genuine failure is rerun along with the noise. A pipeline nobody believes is worse than none, because it costs time and provides no safety.

## What an assigned team does with CI/CD pipelines.

Deployment frequency is a good proxy for delivery health. Teams deploying several times a day have small changes, fast feedback and low-risk releases; teams deploying monthly have the opposite, and usually a release process that requires a meeting.

Improving that is a delivery-path concern rather than an application one, scoped under [devops as a service](https://azendo.co/services/cloud-and-devops/) alongside the development capacity.

## What we use CI/CD pipelines for.

* Feedback fast enough to change behaviour A pipeline that returns in minutes, so changes stay small and frequent.
* A suite the team believes Flakiness treated as a defect, because reruns train people to ignore failures.
* Deployment as a routine event Releases that do not require a meeting or a named individual.

## How CI/CD pipelines capacity is assigned.

Pipeline reliability is treated as a product rather than as configuration, maintained continuously within an agreed [committed monthly capacity](https://azendo.co/pricing/).

## Industries that ask for it

* [SaaS and technology](https://azendo.co/industries/saas-and-technology/)

## Related in ci and delivery

* [GitHub Actions — skill we assign for](https://azendo.co/skills/github-actions/)
* [Jenkins — skill we assign for](https://azendo.co/skills/jenkins/)
* [GitLab CI — skill we assign for](https://azendo.co/skills/gitlab-ci/)
* [Fastlane — skill we assign for](https://azendo.co/skills/fastlane/)
* [Codemagic — skill we assign for](https://azendo.co/skills/codemagic/)
* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)

## Tell us what your roadmap needs CI/CD pipelines for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)