- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- Build and Release Lead
- Code
- ENG-12
It diagnoses failed and slow builds and deployments for the company's applications, telling a broken change from a flaky test, an expired credential, a runner shortage or a dependency outage, and proposes the fix. It re-runs routine failures within the budget and sends anything touching protected gates, or deployment to systems at operating sites, to the approver. **The problem it solves:** Why the build or deployment failed or slowed: the failing stage, the logs and recent changes, and which of a broken change, flaky test, credential, runner or dependency fault explains it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CI system: the run, its logs and recent changes..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Build and Release Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CI system: it re-runs or fixes routine pipeline problems. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The pipeline standards: stages, protected gates, deployment windows for site systems (never during a turnaround start-up or an active emergency) and runner capacity.
Reads from
the CI system: the run, its logs and recent changes.
Acts in
the CI system: it re-runs or fixes routine pipeline problems.
Hands back
An object with cause, evidence, fix, retried (true or false) and alternatives.
Asks a person when
The fix touches a protected gate, a credential, or a deployment to an operating site.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Build time budget (minutes) | 15 | Per pipeline. |
| Flaky threshold (%) | 5 | Failure rate on rerun that marks a test flaky. |
| Retries | 1 | For routine failures. |
| Protected gates | required tests, security scan, production deploy approval, site deployment window | Comma-separated. |
| Main red alert (minutes) | 30 | Main branch red this long alerts the team. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Tell a broken change from a flaky test, credential, runner or dependency fault with evidence.
- Retry routine failures 1 time.
- Never bypass required tests, security scan, production deploy approval, site deployment window, and never deploy to an operating site outside its agreed window.
- Alert when main is red for 30 minutes and keep builds within 15 minutes.
See the CI/CD Pipeline Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.