# buildpulse-test-reporter を Homebrew でインストール

buildpulse-test-reporter のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

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

追加のインストールコマンド:

### macOS

- Homebrew (100%):

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

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:buildpulse-test-reporter
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.29.0
- **ソース概要:** Connect your CI to BuildPulse to detect, track, and rank flaky tests
- **ホームページ:** <https://buildpulse.io>
- **リポジトリ:** <https://github.com/buildpulse/test-reporter>
- **最終更新:** 2026-07-26T10:56:36+02:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- buildpulse-test-reporter (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 0.29.0
## プロジェクトの歴史と使われ方

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.

### プロジェクトの歴史

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.

### 採用の歴史

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.

### 使われ方

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.

### パッケージ好きにとっての重要性

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.

### タイムライン

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

### ソース

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


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- 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)


## ソース

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