How does Deviera detect flaky tests?

Deviera watches the result of every CI run over a rolling 7-day window and looks for tests that alternate between pass and fail without the code changing. Those alternating patterns are the classic signature of a flaky test, and they are flagged automatically so you can fix or quarantine them instead of hitting “re-run” and hoping.

What CI providers does it work with?

GitHub Actions and GitLab CI. Deviera receives run results over webhooks in real time — there is no agent to install in your pipeline and no build configuration to change. Connect the repository and CI Intelligence starts watching the next run.

What is a Repo Health Score?

A single 0–100 score per repository — higher is better — that combines failure rate, flakiness, and the recent trend direction. It gives you a fast way to rank repos and triage the worst offenders first, and it updates after every CI run.

Will I get an issue for every single failed run?

No. Deviera creates one issue per failure streak, not one per run, and a configurable cooldown prevents duplicate issues for the same ongoing outage. That keeps a long-running failure from flooding your tracker — you get one actionable ticket with full context instead of dozens of duplicates.

What does Team Flow track?

Team Flow measures how long pull requests wait for a first review and whether a repo is breaching its work-in-progress (WIP) limits. It gives you per-repo visibility into where review bottlenecks are forming so you can rebalance reviewers before the backlog compounds.

How fast does it act when CI breaks?

Very fast. Because detection is webhook-driven, a tracking issue is typically created within about 30 seconds of a failure, and team notification follows within a few minutes — long before someone would notice by manually checking the pipeline.

CI Intelligence, Repo Health & Team Flow

Know which pipelines are
quietly breaking.

Deviera watches every CI run across all your repos, detects flaky tests and broken pipelines, scores each repo's health, tracks PR review wait time and WIP breaches with Team Flow, and creates Linear or Jira issues the moment something goes wrong — automatically.

Start monitoring for free View pricing →

14-day free trial · No credit card required

Deviera CI Intelligence dashboard showing repo failure rates, flaky detections, and status badges — CI Intelligence — every repo, every pipeline, ranked by failure rate and flakiness.

CI Intelligence — last 30 days4 repositories monitored

Repository	Status	Failure rate	Flaky	Runs	Saved
api-service	broken	38%	4	120	42 min
frontend	flaky	14%	7	210	31 min
auth-service	stable	2%	0	85	0 min
data-pipeline	unstable	21%	2	64	18 min

Repo Health Scores

0 = critical · 100 = perfect

api-service42

data-pipeline61

frontend74

auth-service96

Deviera repo health dashboard with per-repo scores, trend charts, and status indicators — Repo Health — one score per repo, updated after every CI run.

Flaky test detection

Identifies tests that alternate between pass and fail on the same commit — the silent killer of CI confidence.

Failure rate trending

Track failure rates over 7, 14, or 30 days. Spot repos trending toward instability before they break.

Repo health scores

A single 0–100 health score per repo, factoring in failure rate, flakiness, and recent trend direction.

Auto issue creation

When CI breaks, Deviera creates a Linear or Jira issue automatically — with repo, branch, run ID, and failure context.

Cross-repo dashboard

All your repos in one view. Sort by health score, failure rate, or flaky detections to triage the worst offenders first.

Cooldown & dedup

One issue per failure streak, not one per run. Configurable cooldown prevents alert fatigue on long-running outages.

Team Flow — review wait time

Track how long PRs wait for a first review and how many repos are breaching your WIP limits. Per-repo visibility into where review bottlenecks are forming.

WIP breach detection

Configurable WIP limits per repo. When the number of open PRs exceeds the threshold, Team Flow flags the repo so you can unblock reviewers before the bottleneck compounds.

How it works

GitHub webhook

Every push to a status check triggers a webhook. Deviera receives the run result in real time.

Pattern analysis

Deviera checks failure rate, flaky patterns (alternating pass/fail), and streak length against your configured thresholds.

Automated action

A Linear issue is created with full context. Cooldown prevents duplicate issues for the same ongoing failure.

< 30s

Time from CI fail to Linear issue

< 5 min

Median time from CI fail to team notification

7-day

Flaky detection window

First CI failure detected within minutes of connecting GitHub

Connect GitHub, enable a CI automation, and let Deviera watch your pipelines around the clock.

Start free — no credit card Read the docs

Frequently asked questions

Related resources

BlogCI/CD failure tracking: why deploy errors need structured tickets BlogThe real cost of a broken main branch BlogHow to detect flaky tests automatically with CI pattern analysis BlogGitLab CI automation: turning pipeline failures into actionable tickets ToolCI Health Score Calculator — free tool GuideEngineering benchmarks by team size

Know which pipelines arequietly breaking.