---
id: "29c9ecbe-2ddd-4657-895e-65aa08be0797"
type: "Software product"
name: "BuildPulse"
slug: "buildpulse"
canonical: "https://groundingwiki.com/en/products/buildpulse/"
markdown: "https://groundingwiki.com/en/products/buildpulse/index.md"
language: en
same_as:
  - "https://buildpulse.io/"
---

# BuildPulse

BuildPulse is a software platform for analysing continuous-integration test results, detecting flaky tests and tracking test reliability. [1] [2]

The markers cite the evidence for the underlying claims. They do not mean one source contains this full sentence.

## Core facts

- **Entity type:** Software product

- **Official website:** [buildpulse.io](https://buildpulse.io/) — [2] first-party, checked 24 Sept 2026

- **API:** Available — [3] first-party, checked 24 Sept 2026

## What is BuildPulse?

BuildPulse combines hosted continuous-integration runners with software for analysing test results and build performance. Its product areas include flaky-test detection and quarantine, code-coverage reporting, repository-level engineering metrics, and an opt-in AI code-review feature. The workflows described by the product rely on CI run data, test reports, or pull requests; availability and setup differ by component. — [4] first-party, checked 3 Oct 2026

## Features and capabilities

### Data & platforms — [5] first-party, checked 24 Sept 2026

- Reports and data exports

### Additional capabilities — [6] first-party, checked 3 Oct 2026; [1] first-party, checked 24 Sept 2026; [3] first-party, checked 24 Sept 2026; [7] first-party, checked 3 Oct 2026; [8] first-party, checked 3 Oct 2026; [9] first-party, checked 3 Oct 2026

- Ci Engineering Metrics: Calculates per-repository pass rate, test volume, build duration and flaky-test disruption from ingested CI data.

- Flaky Test Detection: Identifies tests with inconsistent outcomes across runs and keeps test history.

- Test Quarantine: Provides controls to quarantine identified flaky tests while they are investigated.

- Code Coverage Reporting: Displays line and branch coverage trends, including branch-level and file-level breakdowns from LCOV or Cobertura reports.

- Hosted Ci Runners: Runs CI jobs on managed Linux runners with runner choices for GitHub Actions, Semaphore and CircleCI workflows.

- Pull Request Code Review: Provides opt-in, early-access AI review comments on pull requests, focused on correctness issues rather than style.

## Integrations

### GitHub — [10] first-party, checked 24 Sept 2026

- **integrates with:** [GitHub](https://groundingwiki.com/en/organizations/github/index.md)

## API

The cited technical and commercial details describe the available programmatic interface.

- **Documentation:** [docs.buildpulse.io/flaky-tests/guides/Test%20Quarantining](https://docs.buildpulse.io/flaky-tests/guides/Test%20Quarantining) — [3] first-party, checked 24 Sept 2026

- **Authentication:** Bearer API key — [3] first-party, checked 24 Sept 2026

## Products

- **AI Code Review:** BuildPulse documents an AI code-review feature that posts pull-request reviews focused on correctness issues. The product page identifies it as early access and says use is opt-in per repository; this is not evidence that the feature is generally available. — [9] first-party, checked 3 Oct 2026

- **Code Coverage:** Coverage reports can be uploaded with test results in LCOV or Cobertura XML format. The interface presents trends over time and per-branch and per-file line and branch coverage; repository thresholds can produce a commit status. — [7] first-party, checked 3 Oct 2026

- **Engineering Metrics:** Repository-level engineering metrics include test pass rate, test volume, build duration and flaky-test disruption. The documentation describes 7-, 30- and 90-day views and says the metrics are derived from CI and test data received by BuildPulse. — [6] first-party, checked 3 Oct 2026

- **Flaky Test Analysis:** Flaky-test analysis uses uploaded JUnit XML/test results to identify tests whose outcomes vary across runs, retain their history and rank their disruption; the product also documents quarantine controls. — [1] first-party, checked 24 Sept 2026

- **Github Action:** The public BuildPulse test-reporter GitHub Action uploads test reports and associated CI metadata to BuildPulse; its repository also documents a wrap mode that collects resource-use data. — [11] first-party, checked 3 Oct 2026

- **MCP Server:** BuildPulse offers a Model Context Protocol server for AI clients to query CI test analytics; its documentation describes both a hosted remote endpoint and a local npm-based stdio option. — [12] first-party, checked 3 Oct 2026

- **Runners:** Hosted Linux CI runners are offered as a drop-in replacement for GitHub Actions, Semaphore and CircleCI hosted runners; the documented workflow change is to change the runner label or resource class while retaining the job steps. — [8] first-party, checked 3 Oct 2026

## Operating model

- **Ci Data:** The analytics products process CI data supplied through test-result uploads or supported provider integrations; coverage data is an optional input that can be sent alongside test results. — [7] first-party, checked 3 Oct 2026

- **Runner Usage:** Runner infrastructure is usage-metered per minute; the product page states that an account receives a monthly free-minutes allocation. Rates and included amounts are time-sensitive and should be checked against the current pricing page. — [8] first-party, checked 3 Oct 2026

## Sources
1. [Flaky Tests Overview](https://docs.buildpulse.io/flaky-tests/overview)
   - Publisher: BuildPulse documentation
   - Type: first-party
   - Checked: 24 Sept 2026
   - Evidence:
     - Definition: "BuildPulse describes its product as CI observability software for detecting flaky tests and tracking test reliability."
     - Additional capabilities: "The official overview lists flaky-test detection and history as core product functions."
     - Flaky Test Analysis: "The overview lists flaky-test detection and history, impact metrics, reporting, notifications, code coverage, quarantine and API access; it specifies JUnit XML as the input."
2. [BuildPulse](https://buildpulse.io/)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 24 Sept 2026
   - Evidence:
     - Definition: "The product site describes BuildPulse as a platform for CI analytics, test reliability and flaky-test detection."
     - Official website: "The product site identifies itself as BuildPulse and links to product information and documentation."
3. [Test Quarantining and API](https://docs.buildpulse.io/flaky-tests/guides/Test%20Quarantining)
   - Publisher: BuildPulse documentation
   - Type: first-party
   - Checked: 24 Sept 2026
   - Evidence:
     - API: "The quarantine guide documents an authenticated API endpoint for querying flaky tests and quarantine status."
     - Additional capabilities: "The official guide documents test quarantine controls and the related API."
     - Documentation: "The official guide provides the Quarantine API endpoint, authentication header and supported request parameters."
     - Authentication: "The API guide specifies a bearer token in the Authorization header for requests."
4. [Products](https://buildpulse.io/products)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - What is BuildPulse?: "The product overview distinguishes hosted CI runners, flaky-test analysis, code coverage, engineering metrics and an opt-in per-repository AI code-review feature."
5. [Flaky Tests Dashboard](https://docs.buildpulse.io/flaky-tests/guides/Flaky%20Tests%20Dashboard)
   - Publisher: BuildPulse documentation
   - Type: first-party
   - Checked: 24 Sept 2026
   - Evidence:
     - Data & platforms: "The official dashboard includes reports and metrics for flaky tests, build history and code coverage."
6. [Engineering Metrics](https://buildpulse.io/products/engineering-metrics)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - Additional capabilities: "The metrics page names the measures and states that they are calculated from BuildPulse-ingested CI and test data."
     - Engineering Metrics: "The metrics page lists per-repository pass rate, test counts, duration and flaky-test disruption, with 7/30/90-day windows based on ingested CI data."
7. [Code Coverage](https://buildpulse.io/products/code-coverage)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - Additional capabilities: "The coverage page documents supported report formats, trend charts and per-file/per-branch coverage views."
     - Code Coverage: "The coverage documentation specifies LCOV/Cobertura inputs, per-branch and per-file views, line/branch tracking, and threshold-based commit statuses."
     - Ci Data: "The coverage guide says coverage can be passed on the same upload step as test results and is optional."
8. [BuildPulse Runners](https://buildpulse.io/products/runners)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - Additional capabilities: "The runner page calls the service a drop-in replacement for hosted runners from these three CI providers."
     - Runners: "The runner guide names GitHub Actions, Semaphore and CircleCI and shows the configuration-level runner selector changes."
     - Runner Usage: "The runner page states per-minute billing and a monthly free-minutes allocation; exact price values are intentionally not asserted here."
9. [AI Code Review](https://buildpulse.io/products/ai-features)
   - Publisher: BuildPulse
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - Additional capabilities: "The AI feature page labels the feature early access, opt-in per repository and focused on correctness review."
     - AI Code Review: "The AI Code Review page describes correctness-focused pull-request review, opt-in per repository and early-access availability."
10. [GitHub Actions integration](https://docs.buildpulse.io/Guides/CI%20Providers/Github%20Actions)
   - Publisher: BuildPulse documentation
   - Type: first-party
   - Checked: 24 Sept 2026
   - Evidence:
     - GitHub: "BuildPulse’s official guide describes its GitHub Actions integration for uploading test results and coverage reports."
11. [BuildPulse test reporter GitHub Action](https://github.com/buildpulse/buildpulse-action)
   - Publisher: BuildPulseLLC on GitHub
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - Github Action: "The project README documents a GitHub Action for uploading test results and metadata and a wrap mode for resource measurements."
12. [MCP Server documentation](https://platform.buildpulse.io/docs/mcp)
   - Publisher: BuildPulse Platform documentation
   - Type: first-party
   - Checked: 3 Oct 2026
   - Evidence:
     - MCP Server: "The MCP documentation identifies hosted and stdio connection modes and describes read-oriented tools for BuildPulse test data."

HTML version: https://groundingwiki.com/en/products/buildpulse/
Methodology: https://groundingwiki.com/methodology/
Source policy: https://groundingwiki.com/source-policy/
Corrections: https://groundingwiki.com/corrections/?entity=BuildPulse
