DEVOPS
Nightly Flaky-Test Scan from JUnit Reports with Linear Rollup
Each night this workflow scans stored JUnit XML results, computes per-test flake rates over a rolling window, auto-skips any test above the threshold for one cycle.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionPull rolling-window JUnit reports from S3AWS S3
- LogicCompute flake rate and select tests over threshold
- ActionCommit one-cycle skip annotations to the repoGitHub
- OutputCreate or update a Linear issue per quarantined testLinear
What it does
Instead of reacting to a single failure, this scheduled job looks at the trailing pass/fail history of every test and flags the ones that are statistically unreliable. Tests crossing the flake-rate threshold are quarantined and tracked in Linear.
When to use it
Use it when single-run detection is too noisy and you want flakiness judged on a trend. Good for large suites where one bad run shouldn't quarantine a test but a 15 percent flake rate should.
How it works
- 1A nightly schedule triggers the scan.
- 2The workflow pulls the last N days of JUnit XML reports from the S3 results bucket.
- 3A logic step computes each test's flake rate and selects those above the configured threshold.
- 4It commits skip annotations to the repo for the selected tests, tagged for one cycle.
- 5For each quarantined test it creates or updates a Linear issue with the flake rate and history link, assigned to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.