Skip to main content
CI/CD Health & Remediation owns whether your merge path can be trusted. It quarantines the stages that fail for no reason, attacks the queue time that makes people stop running things, and catches a broken delivery stage early. This page covers the outcome the module owns, the two workflows inside it, and what it needs connected.

What this module owns

A merge pipeline degrades quietly. One stage starts failing intermittently, people learn to re-run it, and re-running becomes reflex — at which point the suite has stopped being a signal and started being a toll. Queue time grows the same way: nobody notices the day it crosses from two minutes to twenty, but by then engineers batch their pushes and review cycles get slower. Neither shows up as an incident, and both are measurable. This module treats the delivery path as something with health worth tracking: which stages fail, how often, for real reasons or not, and what that costs in waiting. Good looks like a suite whose failures are believed, a queue time nobody works around, and a quarantine list that shrinks because quarantined stages get fixed rather than forgotten.

The workflows inside it

This module contains 2 workflows.

Flaky stage quarantine

Runs on a schedule you set. It identifies the stages failing intermittently rather than meaningfully, quarantines them so they stop blocking merges, and keeps the list visible so a quarantine is a temporary state with an owner rather than a permanent exemption.

Queue-time & failure-rate triage

Runs on a schedule. It reports where time actually goes in the merge path — queueing versus running — and which stages carry the failure rate, then proposes the change that removes the biggest share.

What it needs connected

Enabling it

1

Open Modules → Overview

CI/CD Health & Remediation appears in the AI Software Operations family with the two workflows it contains.
2

Turn it on

Enabling the module adds it to your sidebar.
3

Point it at your merge path

Connect the build system and the repositories it serves, then decide whether a quarantine is applied automatically or proposed for review.

What you see when it runs

Each finding is a record: the stage, its failure rate, whether those failures were real, the time it costs, and what the module proposes. Quarantines carry an owner and the date they started, so the list reads as debt rather than as configuration.

Next steps

Change Intelligence & Risk Control

Judge the production impact of a change after it leaves the merge path.

Production Readiness & Standards

Gate release candidates against the standards required for production.

Approvals

How a quarantine reaches a human decision.