Automic VaultAutomic Vault

brew

Install buildpulse-test-reporter with Homebrew

Connect your CI to BuildPulse to detect, track, and rank flaky tests. Version 0.29.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install buildpulse-test-reporter

local Homebrew formula metadata

overview

Package summary

Connect your CI to BuildPulse to detect, track, and rank flaky tests

Commands and aliases

  • buildpulse-test-reporter

history

Project history and usage

BuildPulse Test Reporter is a small CI upload/reporting CLI for BuildPulse's flaky-test product. Its public role is to connect test output from CI systems to buildpulse.io so BuildPulse can detect, track, and rank flaky tests.

Project history

The `buildpulse/test-reporter` repository was created on 2020-07-19. The README describes the project as a binary that connects continuous integration to BuildPulse and documents platform-specific downloads, local builds with GoReleaser, and standalone submission commands.

The project is intentionally narrow: it is not a general test runner, but an integration binary that packages BuildPulse upload behavior for Linux, macOS, and Windows CI environments.

Adoption history

Public adoption is limited and mostly product-driven. The README lists native environment-variable inference for GitHub Actions, Buildkite, CircleCI, Jenkins, Semaphore, Travis CI, Webapp.io, AWS CodeBuild, Bitbucket Pipelines, and Azure DevOps Pipelines.

For GitHub Actions users, the README points to `buildpulse-action` as a wrapper around the binary, which is the likely common path for teams already using BuildPulse.

How it is used

Users run `buildpulse-test-reporter submit` with a test report path plus BuildPulse account and repository identifiers. In unsupported CI environments, they provide commit, branch, build URL, organization, and repository metadata through environment variables.

The command also accepts coverage files, tags, quotas, repository directory, or tree SHA, making it a CI metadata bridge rather than a local developer workflow tool.

Why package nerds care

Its significance is modest but real for package-manager catalogs: it is an example of a vendor SaaS integration CLI that gets packaged so CI scripts can pin or install a normal executable instead of copying curl snippets.

The interesting packaging detail is cross-platform binary distribution for a narrow CI function, with Homebrew acting as a convenient macOS developer and CI install path.

Timeline

  • 2020: Public `buildpulse/test-reporter` repository is created.
  • 2020s: README documents packaged binaries for Linux, macOS, and Windows and native support for common CI providers.
  • 2025: Repository metadata shows recent upstream activity, but public project history remains sparse.

Related projects

  • BuildPulse Test Reporter is related to buildpulse.io, BuildPulse flaky-test analysis, `buildpulse-action`, GitHub Actions, Buildkite, CircleCI, Jenkins, Travis CI, and other CI systems.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 8 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
buildpulse-test-reportercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.29.0
manager updated
local dataok
upstreamcurrent
latest detectedv0.29.0

https://github.com/buildpulse/test-reporter

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:buildpulse-test-reporter
Version0.29.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/buildpulse-test-reporter
Homepagehttps://buildpulse.io
Repositoryhttps://github.com/buildpulse/test-reporter
Upstream docshttps://github.com/buildpulse/test-reporter#readme
LicenseMIT
Source archivehttps://github.com/buildpulse/test-reporter/archive/refs/tags/v0.29.0.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebuildpulse-test-reporter
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment