bazelbuild/bazel

Bazel is a build and test system for software of any size, aimed at teams that need fast incremental builds and one consistent tool across languages and repositories. Its pitch is "{Fast, Correct} - Choose two": it avoids unnecessary work without giving up correctness.

What changes in a real workflow

You declare targets and their dependencies, and Bazel works out what actually needs rebuilding. The README credits local and distributed caching, optimized dependency analysis and parallel execution for the speed, and notes that only necessary work is redone. The practical effect is that changing one part of a large codebase or monorepo does not trigger a full rebuild.

The same tool handles Java, C++, Android, iOS, Go and other language platforms on Windows, macOS and Linux. Builds and tests are expressed in one framework, so a single command in CI can cover several languages instead of stitching together separate per-language build scripts. Bazel can work with multiple repositories or one huge monorepo, and the README positions it as scalable across an organization's codebase and continuous integration.

Extending it

Bazel is designed to be extended: you can add support for new languages and platforms in its extension language, and reuse rules published by the community. The documentation covers rules, extending Bazel, the query command and testing in some depth. This matters because non-core language support often comes from community rule sets rather than the core tool.

Requirements and things to know

The README does not state version requirements or platform caveats beyond the OS list. Installation and a first project are covered in the official install and getting-started guides, with tutorials for C++, Java, Android and iOS.

The most decision-relevant caveat comes from outside the README. In a 2019 discussion around the 1.0 release, a commenter said the ecosystem around Bazel was immature, with frequent backward-compatibility breaks that pushed rule authors to keep up; another ruleset maintainer in the same thread reported the upgrade path as busy but manageable ecosystem concerns, maintainer's experience. These are dated opinions about an older release, not current evaluation, but they point to the cost of depending on third-party rules and to watching upgrade notes when adopting.

Security issues are handled by email with a stated response target of three working days and a 90-day disclosure timeline. The project is Apache-2.0 licensed.