ENGINEERING
Flaky-Test Quarantine Orchestrator (GitLab CI)
Detects a test that passed on retry in GitLab CI, marks it as quarantined by opening a tracking issue, and pings the last engineer who touched the test file.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline completed webhookGitLab
- ActionFetch job traces and parse retry resultsGitLab
- LogicKeep only fail-then-pass-on-retry tests
- ActionResolve last author via commits APIGitLab
- ActionCreate or update flaky-test tracking issueGitLab
- OutputNotify last toucher in SlackSlack
What it does
When a GitLab CI pipeline finishes, this workflow inspects the job logs for tests that failed on a first attempt but passed on retry — the signature of a flaky test. For each one it confirmed flaky, it opens (or updates) a GitLab quarantine tracking issue and notifies the engineer who last modified the test via git blame.
When to use it
Run this on every merge-request and main-branch pipeline once you've enabled job retries. It keeps intermittently failing tests from eroding trust in CI without forcing anyone to babysit the pipeline page.
How it works
- 1A GitLab pipeline-completion webhook fires with the pipeline and job IDs.
- 2The flow pulls each job's trace and parses retry markers to find tests that flipped fail-then-pass.
- 3A logic step filters to genuinely flaky cases (passed on retry, same commit) and drops hard failures.
- 4For each flaky test it resolves the last author via the GitLab commits API on the test path.
- 5It creates or updates a labeled `flaky-test` issue in GitLab with the test name, failure rate, and trace excerpt.
- 6It posts a Slack message tagging the last toucher with a link to the issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.