| commit | 2ba818ca7d2c77f517f1c0e6540c9af0501b7fb2 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Jun 15 16:42:06 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Thu Jun 16 09:00:37 2016 +0000 |
| tree | 9b785005db473fbcba905b53ed2d6e715c644f07 | |
| parent | 13221745065e24bb5dab3340ff13afabae7bc864 [diff] |
Rollback of commit df39a8a06e32aa864d2504df1ea2c7ed162c8c1d. *** Reason for rollback *** Broke a few projects, including many targets in AGSA: [] *** Original change description *** Ensure manifest merger places the application element as the last child of the manifest element. This is required for Android N. RELNOTES: Merged manifests are guaranteed to have the application element as the last child of the manifest element as required by Android N. -- MOS_MIGRATED_REVID=124960831
{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.