| commit | 1a3603a8a9441d7438a3925f0af0c8ff2abb1e06 | [log] [tgz] |
|---|---|---|
| author | Adam Michael <ajmichael@google.com> | Tue Oct 25 22:20:08 2016 +0000 |
| committer | John Cater <jcater@google.com> | Wed Oct 26 11:11:01 2016 +0000 |
| tree | e1849d47b0863f5826e4677f8f5c22fce4e4dcad | |
| parent | 97cc5be8787145bd0402406b67b2a28df5348788 [diff] |
Fix zip_manifest_creator dep in bazel_tools repo with an alias. In commit 78c19807d2cbb308b830022dcdcc8b03f19f90a9 I accidentally broke aar_import when I moved zip_manifest_creator from tools/android to tools/zip because tools/android does not have separate BUILD and BUILD.tools files. The test did not catch this, because the dependency in tools/android/BUILD is correct in the context of the bazel tree but not in the context of the bazel_tools embedded workspace. -- MOS_MIGRATED_REVID=137209500
{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.