macOS
Homebrewverifiziert · 100%
brew install buildpulse-test-reporterlocal Homebrew formula metadata
brew
buildpulse-test-reporter mit Homebrew installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für buildpulse-test-reporter in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Connect your CI to BuildPulse to detect, track, and rank flaky tests
Projektlinks
Befehle und Aliase
- buildpulse-test-reporter
Verlauf
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
Sicherheitslage
Risikostufe: grün
narrow executable package without higher-risk signals.
Risikoklassifikator
grün Risiko · niedrig Konfidenz · appliance
Warum
- narrow executable package without higher-risk signals
Signale
- metadata:no-higher-risk-signals
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
- Build-Metadaten listen 1 Build-Abhängigkeiten.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
buildpulse-test-reporter | cli | globales Executable |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-07-08
Manager-Version0.29.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.29.0
https://github.com/buildpulse/test-reporter
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:buildpulse-test-reporter |
|---|---|
| Version | 0.29.0 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/buildpulse-test-reporter |
| Homepage | https://buildpulse.io |
| Repository | https://github.com/buildpulse/test-reporter |
| Upstream-Dokumentation | https://github.com/buildpulse/test-reporter#readme |
| Lizenz | MIT |
| Quellarchiv | https://github.com/buildpulse/test-reporter/archive/refs/tags/v0.29.0.tar.gz |
| Build-Abhängigkeiten | go |
| Bottle | verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | buildpulse-test-reporter |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- 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