commit | dd714256e87c7d5f13f1e3308132d6696d47c067 | [log] [tgz] |
---|---|---|
author | Thiago Farina <tfarina@chromium.org> | Thu May 07 11:41:35 2015 +0000 |
committer | Lukacs Berki <lberki@google.com> | Thu May 07 14:05:51 2015 +0000 |
tree | 338e0d3958c68119e4ac590efd4421c3e2e8ff68 | |
parent | 1c5ba82efc1b1ca47f2123e3f1f894e539ee68f7 [diff] |
Cleanup: Remove GetJvm() function declaration. There is no implementation and thus nobody is calling/using it. -- Change-Id: I2cf184e3d80eb0ef2b04ea4617697e8426cc7a58 MOS_MIGRATED_REVID=93018104
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.
How to install Bazel
How to get started using Bazel
The Bazel command line is documented in the user manual
The rule reference documentation is in the build encyclopedia
How to use the query command
How to extend Bazel
The test environment is described in the test encyclopedia
About the Bazel project: