- Industry
- Retail
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- Head of Platform
- Code
- ENG-12
It maintains the build and deployment pipelines for the storefront, app, commerce services and the store till software, and explains why a pipeline is failing or slow, separating flaky tests, broken dependencies, environment drift and real defects. It proposes the fix and enforces the peak trading freeze in the pipeline. **The problem it solves:** Why the pipeline is failing, slow or blocked, and which cause the evidence supports.
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/CD pipeline: the recent runs, stage timings, logs and pipeline changes 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 Head of Platform with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CI/CD pipeline: it opens the pipeline fix and quarantines confirmed flaky tests with a ticket. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The pipeline guide: the pipelines and stages, the deployment strategies (blue-green for the storefront, staged rollout for tills), the freeze calendar, known flaky tests and the build cache setup.
Reads from
the CI/CD pipeline: the recent runs, stage timings, logs and pipeline changes for the pipeline named.
Acts in
the CI/CD pipeline: it opens the pipeline fix and quarantines confirmed flaky tests with a ticket.
Hands back
An object with likely_cause, alternative_causes (a list of cause and why_less_likely), evidence (a list), fix (a list of steps), flaky_tests (a list) and deploy_blocked (true or false).
Asks a person when
The fix changes deployment to production or tills, or an emergency deploy is needed in the freeze.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Build time target (minutes) | 15 | A pipeline slower than this is investigated. |
| Pilot stores for till releases | 5 | Till software deploys to this many pilot stores before the estate. |
| Block deploys in the trading freeze | On | When on, production deploys are blocked in the freeze unless an emergency change is approved. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Weigh flaky tests, dependency breaks, environment drift and real defects before naming a cause, and say what evidence separates them.
- A pipeline slower than 15 minutes gets its slowest stages profiled.
- Till software deploys to 5 pilot stores, overnight, before any wider rollout.
- When on is true, block production deploys in the trading freeze unless an emergency change is approved.
- Never skip or delete a failing test to make a pipeline pass.
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.