installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install bazel-remote

local Homebrew formula metadata

Linux

Nixvérifié · 92%

nix profile install nixpkgs#bazel-remote

nixpkgs package indexes · pkgs/by-name/ba/bazel-remote/package.nix · Source: api.github.com

aperçu

Résumé du paquet

Remote cache for Bazel

Liens du projet

Commandes et alias

bazel-remote

historique

Historique du projet et usages

bazel-remote is a standalone HTTP/1.1 and gRPC remote build cache for Bazel and other REAPI clients, optimized for teams that want remote cache performance without operating a full remote execution service.

Historique du projet

The project began in August 2017 as a basic HTTP cache and grew into a production remote-cache server with disk storage, least-recently-used eviction, S3 and GCS backends, gRPC support, REAPI compatibility, and Prometheus-friendly operational endpoints.

Its README reports that bazel-remote has served terabytes of cache artifacts per day since April 2018 on commodity hardware and AWS servers, which is unusually explicit operational history for a package-manager formula.

Historique d'adoption

bazel-remote became useful as Bazel users adopted remote caching to make monorepo and CI builds faster without adopting remote execution at the same time.

Homebrew and Nix packaging reflect its role as deployable infrastructure: users install a single binary, point Bazel at its HTTP or gRPC endpoint, and size local disk or cloud-backed storage for their build workload.

Modes d'utilisation

Operators configure a cache directory, maximum cache size, HTTP and/or gRPC listener, optional TLS/authentication, and optional proxy backends through flags, environment variables, or a YAML config file.

Bazel clients use bazel-remote for action-cache and content-addressable-storage reads and writes, while the server exposes /status, CAS test endpoints, metrics, and optional Remote Asset API support.

Pourquoi les passionnés de paquets s'y intéressent

bazel-remote is package-nerd interesting because it packages build acceleration as a small Go service rather than a SaaS product or heavyweight cluster.

It sits at the boundary between package manager convenience and fleet infrastructure: a Homebrew-installed binary can be enough for local experiments, but the same executable can serve multi-terabyte-per-day CI traffic.

Chronologie

2017-08: Upstream git history starts with an initial HTTP cache implementation.
2018-04: README reports bazel-remote serving terabytes of cache artifacts per day from this period onward.
2020s: README documents HTTP/1.1, gRPC REAPI, cloud proxy backends, zstd compressed blobs, and operational endpoints.

Related projects

Bazel is the primary client and provides remote cache flags used with bazel-remote.
bazelbuild/remote-apis defines the REAPI services that bazel-remote implements in part.
Remote execution systems can use bazel-remote as a cache component or as a simpler alternative when execution offload is unnecessary.

Sources

Upstream git history for https://github.com/buchgr/bazel-remote starts in August 2017.
https://github.com/buchgr/bazel-remote#readme documents project purpose, production-use history since April 2018, APIs, storage backends, configuration, and auth.
source_facts.package-manager-url records the Homebrew packaging surface.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

narrow executable package without higher-risk signals

Signaux

metadata:no-higher-risk-signals

Comportement d'installation

Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: path passed with --config_file$BAZEL_REMOTE_CONFIG_FILE

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: path passed with --htpasswd_file$BAZEL_REMOTE_HTPASSWD_FILE

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`bazel-remote`	cli	exécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-08

version du gestionnaire2.6.1

gestionnaire mis à jour

données localesOK

amontà jour

dernière version détectéev2.6.1

https://github.com/buchgr/bazel-remote

infoNo package-manager update timestamp was available.confiance faible

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:bazel-remote
Version	2.6.1
Gestionnaire de paquets	Homebrew
Page du gestionnaire de paquets	https://formulae.brew.sh/formula/bazel-remote
Page d'accueil	https://github.com/buchgr/bazel-remote/
Dépôt	https://github.com/buchgr/bazel-remote
Docs amont	https://github.com/buchgr/bazel-remote#readme
Licence	Apache-2.0
Archive source	https://github.com/buchgr/bazel-remote/archive/refs/tags/v2.6.1.tar.gz
Dépendances de compilation	go
Bouteille	disponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrew	non défini
Service	aucun déclaré

faits du registre

Détails de la base source

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	bazel-remote
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	head stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

bazel-remote

nix profile install nixpkgs#bazel-remote

normalized package name match
Correspondance par : Bazel Remote

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ba/bazel-remote/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/bazel-remote.yml

Sources utilisées

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Installer bazel-remote avec Homebrew, Nix