DEVOPS
Publish a Weekly Flaky-Test Health Digest to Confluence and Slack
Aggregates the week's flaky-test occurrences from GitHub and Datadog into a ranked health report, publishes it as a Confluence page.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionPull weekly flakes from GitHubGitHub
- ActionPull flake-rate stats from DatadogDatadog
- LogicMerge, rank, and compute trend
- ActionPublish ranked report to ConfluenceConfluence
- OutputPost top offenders to SlackSlack
What it does
This workflow turns scattered flaky-test signals into a single weekly scorecard. It tallies how often each test flaked, ranks the worst offenders, computes the week-over-week trend, and publishes a shareable report so flakiness stays visible to the whole team.
When to use it
Use this for a recurring engineering health ritual — a Monday digest that names the top flaky tests, shows whether things are improving, and gives leads an artifact to assign owners against during planning.
How it works
- 1A weekly schedule trigger fires Monday morning.
- 2The flow pulls the past week's rerun-confirmed failures from GitHub and flake-rate stats from Datadog.
- 3A logic step merges and ranks tests by occurrence count and computes the trend versus the prior week.
- 4It renders a Confluence page with the ranked table, trend chart data, and links to each test's open quarantine ticket.
- 5It posts the top five offenders and the Confluence link to the engineering Slack channel.
- 6The published page URL is returned as the output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.