Install bazel with Homebrew, chocolatey, MacPorts, Nix, pacman, scoop, winget, zypper

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• bazel-9.1.0

Project history

The public bazelbuild/bazel repository dates to February 2015 and the project reached Bazel 1.0 on October 10, 2019. The 1.0 announcement marked the start of semantic versioning and stability windows for backward-incompatible releases.

Bazel's official introduction emphasizes a high-level build language, Starlark rules, incremental rebuilds based on file content and commands, local and distributed caching, parallel execution, hermeticity, and scale to 100k+ source files and tens of thousands of users.

The modern Bazel line is shaped by dependency-management and rule-modularization migrations. Bazel 7 turned Bzlmod on by default; Bazel 8 turned the old WORKSPACE mechanism off by default; Bazel 9 is planned to remove WORKSPACE functionality.

Adoption history

Bazel's adoption grew from Google's internal build culture into a public ecosystem of language rules, remote-cache servers, registries, CI tooling, and version managers. The official users page lists companies including Adobe, Asana, Canva, Databricks, Dropbox, Google, LinkedIn, Lyft, Nvidia, Pinterest, Snap, Stripe, Tinder, and Twitter.

Package-manager adoption reflects that cross-platform reach: the input records Bazel packages across Homebrew, Chocolatey, MacPorts, Nix, Arch, Scoop, winget, and zypper.

How it is used

A Bazel workspace defines BUILD files and targets, then users run bazel build, test, run, query, or cquery from the command line. Bazel analyzes dependencies into an action graph and executes only the actions needed for requested outputs.

For repeatable package-manager workflows, .bazelrc files matter: official docs document system, workspace, and user rc files, while Bazelisk and .bazelversion are often used to pin the Bazel version per repository.

Why package nerds care

Bazel is a package-nerd landmark because it made build tools behave more like content-addressed package systems: actions are keyed, cached, queried, remotely shared, and constrained toward hermetic reproducibility.

Its formula history is also interesting because current Homebrew carries both the moving bazel formula and versioned bazel@7 and bazel@8 formulas, acknowledging that Bazel upgrades can be migration events rather than ordinary patch bumps.

Timeline

• 2015-02: Public bazelbuild/bazel git history begins.
• 2019-10-10: Bazel 1.0 is released and the project starts semantic-versioned release stability windows.
• 2023-12-11: Bazel 7.0 LTS is released with Bzlmod, Build without the Bytes, and Skymeld enabled by default.
• 2024-12-09: Bazel 8.0 LTS is released with Bzlmod as the default dependency-management system and WORKSPACE disabled by default.
• 2026: The input's Homebrew formula metadata shows the unversioned bazel formula tracking the Bazel 9 line.

Related projects

• Bazelisk is the companion launcher/version manager that selects and downloads the right Bazel binary for a workspace.
• bazel-remote provides a standalone remote cache for Bazel and other REAPI clients.
• bazel-diff computes impacted Bazel targets between Git revisions for CI test selection.
• Bazel Central Registry and Bzlmod form Bazel's modern module distribution layer.

Sources

• https://bazel.build/about/intro documents Bazel's build/test model, scale, caching, supported platforms, and command-line use.
• https://bazel.build/community/users documents public adopters.
• https://blog.bazel.build/2019/10/10/bazel-1.0.html documents the 1.0 release and semantic-versioning policy.
• https://blog.bazel.build/2023/12/11/bazel-7-release.html documents Bazel 7 defaults including Bzlmod.
• https://blog.bazel.build/2024/12/09/bazel-8-release.html documents Bazel 8, Bzlmod default dependency management, and WORKSPACE being off by default.
• source_facts.package-manager records package-manager availability across ecosystems.