Daily companion to the flaky-test detector. Reads open flaky-test tickets, applies the framework's skip mechanism with a ticket link and a hard expiry date, and opens one PR per run containing the skips. On later runs it re-runs quarantined tests, un-quarantining any that pass consistently, and escalates tickets that remain quarantined past expiry. Set your repository on the Clone step and your ticket integration on the List/Update steps after importing.
- Identifier
test-quarantine-manager- Version
- 1.0.1
- Steps
- 5
- Triggers
- 1
- flaky-tests
- quarantine
- ci
- automated
- test-maintenance
When it runs
schedule.daily- Schedule
- Every day at 06:00 UTC
0 6 * * * - 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.
- 01Daily Schedule (06:00 UTC)
triggerThe event that starts the run.
- 02Clone Repository ⚠️ SET YOUR REPO
git.cloneShallow-clones the repository at the right ref.
- 03List Flaky-Test Tickets
ticket.listQueries the tracker for a set of tickets.
- 04Manage Test Quarantine
agent.runOne agent works the task with its toolkit.
- 05Mark Quarantine Active
ticket.updateMoves status or fields on an existing ticket.
The agent
Test Quarantine Manager
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 50
- Tools
- 10
Tickets · 3
list_ticketsList Tickets · readread_ticketRead Ticket · readupdate_ticketUpdate Ticket · write
Git provider · 3
create_branchCreate Branch · writecreate_or_update_fileCreate or Update File · writecreate_pull_requestCreate Pull Request · write
Filesystem · 2
read_fileRead File · readedit_fileEdit File · write
Terminal · 1
run_terminal_cmdRun Terminal Command · write
Status · 1
update_statusUpdate Status · write
Related playbooks
CI Duration Regression Watch
Weekly analysis of CI durations that identifies regressed jobs, opens the workflow definition, and proposes a specific cause and fix.
Fix CI
Reads CI failure logs, locates the root cause in the diff, and pushes a fix.
Flaky Test Detector
Runs the test suite five times on the same commit and files a ticket for every non-deterministic test.