| commit | 7ba40f811acf86b6326eb0149e8ce6f2201b2e5b | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Feb 08 20:10:46 2017 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Thu Feb 09 15:09:44 2017 +0000 |
| tree | 3011b4d8b71162ccaf8aa76c3d757261d01d76c2 | |
| parent | 92f117f426184d9f097e9fb592b35fb4e8c81a83 [diff] |
Rollback of commit 602a98cbebeff2ba1c2d8605a9552b2c8f5622ae. *** Reason for rollback *** Rolling forward with fixes for the incremental tool. *** Original change description *** Automated [] rollback of commit d11d510c571b10787856395709f9ad945ca70bb2. *** Reason for rollback *** -- PiperOrigin-RevId: 146940409 MOS_MIGRATED_REVID=146940409
{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.