# buildpulse-test-reporter mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für buildpulse-test-reporter in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:buildpulse-test-reporter
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install buildpulse-test-reporter
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:buildpulse-test-reporter
- **Paketmanager:** Homebrew
- **Version:** 0.29.0
- **Quellzusammenfassung:** Connect your CI to BuildPulse to detect, track, and rank flaky tests
- **Homepage:** <https://buildpulse.io>
- **Repository:** <https://github.com/buildpulse/test-reporter>
- **Zuletzt aktualisiert:** 2026-07-26T10:56:36+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- buildpulse-test-reporter (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.29.0
## Projektgeschichte und Nutzung

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

### Warum Paket-Nerds sich dafür interessieren

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.

### Zeitleiste

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

### Quellen

- <https://api.github.com/repos/buildpulse/test-reporter>
- <https://github.com/buildpulse/test-reporter#readme>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/buildpulse-test-reporter.yml](https://github.com/mxcl/pkgdb/blob/main/combined/buildpulse-test-reporter.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph