Software product

BuildPulse

BuildPulse is a software platform for analysing continuous-integration test results, detecting flaky tests and tracking test reliability.[1]first-party sourceFlaky Tests OverviewBuildPulse documentationBuildPulse describes its product as CI observability software for detecting flaky tests and tracking test reliability.CheckedOpen original source [2]first-party sourceBuildPulseBuildPulseThe product site describes BuildPulse as a platform for CI analytics, test reliability and flaky-test detection.CheckedOpen original source

Markdown

On this page

01

Core facts

Entity type
Software product
Official website
buildpulse.io[2]first-party sourceBuildPulseBuildPulseThe product site identifies itself as BuildPulse and links to product information and documentation.CheckedOpen original source
API
Available[3]first-party sourceTest Quarantining and APIBuildPulse documentationThe quarantine guide documents an authenticated API endpoint for querying flaky tests and quarantine status.CheckedOpen original source

02

What is BuildPulse?[4]first-party sourceProductsBuildPulseThe product overview distinguishes hosted CI runners, flaky-test analysis, code coverage, engineering metrics and an opt-in per-repository AI code-review feature.CheckedOpen original source

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.

03

Features and capabilities

Data & platforms[5]first-party sourceFlaky Tests DashboardBuildPulse documentationThe official dashboard includes reports and metrics for flaky tests, build history and code coverage.CheckedOpen original source

  • Reports and data exports

Additional capabilities[6]first-party sourceEngineering MetricsBuildPulseThe metrics page names the measures and states that they are calculated from BuildPulse-ingested CI and test data.CheckedOpen original source [1]first-party sourceFlaky Tests OverviewBuildPulse documentationThe official overview lists flaky-test detection and history as core product functions.CheckedOpen original source [3]first-party sourceTest Quarantining and APIBuildPulse documentationThe official guide documents test quarantine controls and the related API.CheckedOpen original source [7]first-party sourceCode CoverageBuildPulseThe coverage page documents supported report formats, trend charts and per-file/per-branch coverage views.CheckedOpen original source [8]first-party sourceBuildPulse RunnersBuildPulseThe runner page calls the service a drop-in replacement for hosted runners from these three CI providers.CheckedOpen original source [9]first-party sourceAI Code ReviewBuildPulseThe AI feature page labels the feature early access, opt-in per repository and focused on correctness review.CheckedOpen original source

  • 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.

04

Integrations

GitHub[10]first-party sourceGitHub Actions integrationBuildPulse documentationBuildPulse’s official guide describes its GitHub Actions integration for uploading test results and coverage reports.CheckedOpen original source

05

API

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

Documentation
docs.buildpulse.io/flaky-tests/guides/Test%20Quarantining[3]first-party sourceTest Quarantining and APIBuildPulse documentationThe official guide provides the Quarantine API endpoint, authentication header and supported request parameters.CheckedOpen original source
Authentication
Bearer API key[3]first-party sourceTest Quarantining and APIBuildPulse documentationThe API guide specifies a bearer token in the Authorization header for requests.CheckedOpen original source

06

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 sourceAI Code ReviewBuildPulseThe AI Code Review page describes correctness-focused pull-request review, opt-in per repository and early-access availability.CheckedOpen original source
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 sourceCode CoverageBuildPulseThe coverage documentation specifies LCOV/Cobertura inputs, per-branch and per-file views, line/branch tracking, and threshold-based commit statuses.CheckedOpen original source
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 sourceEngineering MetricsBuildPulseThe 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.CheckedOpen original source
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 sourceFlaky Tests OverviewBuildPulse documentationThe overview lists flaky-test detection and history, impact metrics, reporting, notifications, code coverage, quarantine and API access; it specifies JUnit XML as the input.CheckedOpen original source
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 sourceBuildPulse test reporter GitHub ActionBuildPulseLLC on GitHubThe project README documents a GitHub Action for uploading test results and metadata and a wrap mode for resource measurements.CheckedOpen original source
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 sourceMCP Server documentationBuildPulse Platform documentationThe MCP documentation identifies hosted and stdio connection modes and describes read-oriented tools for BuildPulse test data.CheckedOpen original source
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 sourceBuildPulse RunnersBuildPulseThe runner guide names GitHub Actions, Semaphore and CircleCI and shows the configuration-level runner selector changes.CheckedOpen original source

07

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 sourceCode CoverageBuildPulseThe coverage guide says coverage can be passed on the same upload step as test results and is optional.CheckedOpen original source
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 sourceBuildPulse RunnersBuildPulseThe runner page states per-minute billing and a monthly free-minutes allocation; exact price values are intentionally not asserted here.CheckedOpen original source

08

Sources

Reference numbers stay stable across this page and each source appears once, ordered by first visible use.

  1. Flaky Tests Overview

    BuildPulse documentation · first-party source

  2. BuildPulse

    BuildPulse · first-party source

  3. Test Quarantining and API

    BuildPulse documentation · first-party source

  4. Products

    BuildPulse · first-party source

  5. Flaky Tests Dashboard

    BuildPulse documentation · first-party source

  6. Engineering Metrics

    BuildPulse · first-party source

  7. Code Coverage

    BuildPulse · first-party source

  8. BuildPulse Runners

    BuildPulse · first-party source

  9. AI Code Review

    BuildPulse · first-party source

  10. GitHub Actions integration

    BuildPulse documentation · first-party source

  11. BuildPulse test reporter GitHub Action

    BuildPulseLLC on GitHub · first-party source

  12. MCP Server documentation

    BuildPulse Platform documentation · first-party source

Found something that needs review?

Suggest a correction