> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CI/CD Health & Remediation

> Keep the merge path trustworthy — flaky stages quarantined, queue time cut, and a broken delivery stage caught before it blocks everyone.

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

| Requirement               | Why                                                                          | Where to set it up                                                       |
| ------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Your build system         | The module reads stage results, durations, and queue times                   | [Built-in integrations](/manage-your-agents/build/built-in-integrations) |
| Your source host          | So a quarantine or configuration change arrives as a reviewable pull request | [Built-in integrations](/manage-your-agents/build/built-in-integrations) |
| Stage ownership           | A quarantined stage needs an owner, or it becomes permanent                  | [Knowledge base](/manage-your-agents/build/knowledge-base)               |
| A scoped write credential | Where you let the module apply a quarantine rather than propose it           | [Credentials & secrets](/manage-your-agents/build/credentials-secrets)   |

## Enabling it

<Steps>
  <Step title="Open Modules → Overview">
    CI/CD Health & Remediation appears in the AI Software Operations family with the two workflows it contains.
  </Step>

  <Step title="Turn it on">
    Enabling the module adds it to your sidebar.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Change Intelligence & Risk Control" href="/modules-and-workflows/ops-automation/change-intelligence">
    Judge the production impact of a change after it leaves the merge path.
  </Card>

  <Card title="Production Readiness & Standards" href="/modules-and-workflows/ops-automation/production-readiness">
    Gate release candidates against the standards required for production.
  </Card>

  <Card title="Approvals" href="/security-and-governance/controls/approvals">
    How a quarantine reaches a human decision.
  </Card>
</CardGroup>


## Related topics

- [Change Intelligence & Risk Control](/modules-and-workflows/ops-automation/change-intelligence.md)
- [Production Readiness & Standards](/modules-and-workflows/ops-automation/production-readiness.md)
- [Modules & workflows](/modules-and-workflows/overview.md)
- [Built-in integrations](/manage-your-agents/build/built-in-integrations.md)
- [Remediation](/manage-your-agents/build/catalog/remediation.md)