commit | 7de7ea0113d73427d2ee45b4728732eeb0ee3b0a | [log] [tgz] |
---|---|---|
author | juliexxia <juliexxia@google.com> | Wed Oct 04 21:42:01 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Fri Oct 06 19:44:54 2017 +0200 |
tree | 44e72aa973cebf39d708525a6263c7ea7c065063 | |
parent | f531ac9db81b0556b640a4a60d01a2256013b3bc [diff] |
Could be missing something but I don't think this line of documentation is true anymore. Looks like now each build command instantiates its own BuildTool to work with instead of BlazeRuntime holding a single instance that gets re-used. PiperOrigin-RevId: 171047696
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase and Continuous Integration system. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.