| commit | 5e1a420f1b385382a2df5359faf3ae773aa8d61e | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Mar 24 03:12:29 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Fri Mar 24 12:19:27 2017 +0000 |
| tree | 8736029d0bf4beebaffa46af230ab4834738caa8 | |
| parent | 58a615c4941e041d68bceeb68b0d77269f6143f5 [diff] |
Rollback of commit bd40871283a54268945dcb0c47c0326645ffda18. *** Reason for rollback *** Rolling forward with the correct changes to the AndroidResourceMergingAction. Tested manually. *** Original change description *** Automated [] rollback of commit a58f245a4b40c0ef961b1f30d96b16a9349711c3. *** Reason for rollback *** broke over 100k targets, in the depot, see [] *** Original change description *** Move library R generation to a separate action, ensuring the merging happens off the java critical path. -- PiperOrigin-RevId: 151087737 MOS_MIGRATED_REVID=151087737
{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.