Skip to content
← Tools / Skills
ToolBuildPulse/10 trustMetrics-checked

BuildPulse

Flaky-test detection, quarantine, and CI analytics.

Visit official site →

About

BuildPulse detects flaky tests from JUnit XML uploads across all major test frameworks (Cypress, Jest, Playwright, RSpec, Go, Python, and more), then helps teams mitigate them with automatic quarantining, impact metrics, and root-cause data like first/last seen with links to the offending builds. It also offers intelligent test selection — running only tests affected by changed files — plus CI health analytics and PR bots that block merges introducing new flaky tests.

It works with GitHub Actions, Jenkins, Buildkite, and more, but it is a focused point tool: it manages flakiness, it does not fix the underlying test code for you, and pricing details are light on the public listings.

What it can do

  • Automatic flaky-test detection and cataloging
  • Auto-quarantine with Jira, Linear, and GitHub issue tickets
  • Root-cause data: first/last seen, flakiness rates, build links
  • Intelligent test selection based on changed files
  • CI pipeline health analytics and PR bots

Setup

  1. Sign up and install the BuildPulse GitHub App or CI integration.
  2. Upload JUnit XML test reports from your pipeline.
  3. Review the flaky-test catalog, impact metrics, and root-cause links.
  4. Enable auto-quarantine and PR checks to stop new flaky tests at merge time.

Prerequisites

A CI pipeline producing JUnit XML test reports; GitHub, Jenkins, or Buildkite access.

Use cases

codeautomationdata

Works with

Any agent (.md)

Trust score — 7/10

/10 trustMetrics-checked

Scored 7/10 (metrics tier, metrics-v1). Evidence: GitHub Marketplace and Atlassian Marketplace listings confirm flaky detection, quarantine, CI analytics, JUnit XML ingestion; Works with GitHub Actions, Jenkins, Buildkite; Marketplace-based evidence; limited independent review depth; Capped at 7: point-tool scope, thinner public evidence. License: Proprietary SaaS..

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
6.0/10
Maintenance · recency, releases, issue load
6.0/10
Openness · license + docs
4.0/10
Manual review · sanity read + red-flag check
6.0/10
  • · GitHub Marketplace and Atlassian Marketplace listings confirm flaky detection, quarantine, CI analytics, JUnit XML ingestion
  • · Works with GitHub Actions, Jenkins, Buildkite
  • · Marketplace-based evidence; limited independent review depth
  • · Capped at 7: point-tool scope, thinner public evidence

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.