DEVOPS

Weekly flaky-test debt report to Confluence

Each week, gathers all quarantined and flaky-labeled tests, ranks them by age and flake frequency.

CategoryDevOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionFetch flaky/quarantine labeled itemsGitHubGitHub
  • ActionPull matching Linear tickets and ownersLinearLinear
  • LogicRank by age and flake count, flag stale
  • OutputPublish report to ConfluenceConfluenceConfluence

What it does

This template turns scattered quarantine tickets into a single weekly accountability report. It collects every test currently labeled flaky or sitting in quarantine, ranks them by how long they have been parked and how often they flake, and publishes a Confluence page so leadership can see the growing debt and who owns it.

When to use it

Use it when quarantined tests pile up and nobody circles back. The weekly report keeps stale skips visible and creates pressure to actually fix or delete them.

How it works

  1. 1A weekly schedule trigger starts the run.
  2. 2GitHub fetches open issues and PRs carrying the `flaky` or `quarantine` labels.
  3. 3Linear is queried for matching open tickets to attach owners and statuses.
  4. 4A logic step ranks each test by quarantine age and flake count, flagging anything parked beyond the allowed window as stale.
  5. 5The report is published or updated as a Confluence page with totals, the ranked table, and stale-quarantine warnings.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.