CI playbook
CI Duration Regression Watch
Weekly analysis of CI durations that identifies regressed jobs, opens the workflow definition, and proposes a specific cause and fix.
Once a week, pulls the last 30 days of CI runs, computes p50 and p95 duration per job, and identifies jobs whose p95 grew by more than a threshold. For each regressed job it opens the workflow definition and the commits in the regression window and proposes a specific cause and fix. A downstream ticket node files the findings only when regressions are detected; otherwise it files a short 'all clear' note.
- Identifier
ci-duration-regression-watch- Version
- 1.0.1
- Steps
- 4
- Triggers
- 1
- ci
- duration
- regression
- performance
- weekly
- automated
When it runs
schedule.weekly- Schedule
- Every Monday at 07:00 UTC
0 7 * * 1 - Timezone
- UTC
The pipeline
The graph below is the one the workflow opens with in the builder, same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Weekly Schedule (Monday 07:00 UTC)
triggerThe event that starts the run.
- 02Clone Repository ⚠️ SET YOUR REPO
git.cloneShallow-clones the repository at the right ref.
- 03Analyse CI Duration Regression
agent.runOne agent works the task with its toolkit.
- 04File Duration Regression Ticket
ticket.createOpens a ticket on the connected tracker.
The agent
CI Duration Regression Agent
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 40
- Tools
- 6
CI/CD · 2
list_pr_ci_runsList PR CI Runs · readget_ci_run_logsGet CI Run Logs · read
Filesystem · 1
read_fileRead File · read
Terminal · 1
run_terminal_cmdRun Terminal Command · write
Tickets · 1
create_ticketCreate Ticket · write
Status · 1
update_statusUpdate Status · write