- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- IT Manager
- Code
- ENG-12
It diagnoses failed and slow builds and deployments of the hotel software, telling a broken change from a flaky booking journey test, an expired sandbox credential for the PMS or payment provider, a runner shortage or an outage at a partner sandbox, and proposes the fix. It re-runs or fixes routine pipeline problems and sends anything that touches a deployment gate or the peak season freeze for approval. **The problem it solves:** Why the build or deployment failed or slowed: the failing stage, the error, what changed before, and whether a partner sandbox or credential is involved.
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 pipeline runs, logs, test history and runner status for the pipeline named..
- 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 IT Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CI system: it re-runs the pipeline or applies the pipeline fix. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The pipeline runbook: each pipeline's stages and time budget, the partner sandboxes it depends on, credential rotation, the deployment gates and the release freezes.
Reads from
the CI system: the pipeline runs, logs, test history and runner status for the pipeline named.
Acts in
the CI system: it re-runs the pipeline or applies the pipeline fix.
Hands back
An object with cause (broken_change, flaky_test, expired_credential, runner_capacity, partner_sandbox_outage or other), evidence (a list), fix, retried (true or false), owner and confidence.
Asks a person when
The fix changes a deployment gate, rotates a production credential, or would deploy during a release freeze.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Build time budget (minutes) | 15 | A pipeline slower than this is diagnosed for a cause. |
| Failure rate that marks a test flaky (%) | 5 | A test failing intermittently above this rate is flagged. |
| Automatic retries for infrastructure failures | 1 | Runner and network failures are retried this many times. |
| Gates it may never skip | booking journey tests, security scan, PCI DSS checks, production deploy approval | Comma-separated. |
| Main branch red before it escalates (minutes) | 30 | If main stays broken this long it pages the build owner. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Tell the cause apart: a change in the failing commit, a flaky test above 5 percent, an expired partner sandbox credential, runner capacity, or a partner sandbox outage; say what confirms each.
- Retry runner and network failures up to 1 times; never retry a real test failure to make it pass.
- Never skip or weaken booking journey tests, security scan, PCI DSS checks, production deploy approval.
- Escalate to the IT Manager when main has been red for 30 minutes.
- Diagnose any pipeline slower than 15 minutes and name the slowest stage.
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.