| commit | 75aa6a46a304c0ccdf16c5e3dffbc1b98c241adb | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Tue Jan 17 08:56:34 2017 +0000 |
| committer | Vladimir Moskva <vladmos@google.com> | Tue Jan 17 12:15:33 2017 +0000 |
| tree | 0b58187e77b8cfa3653ff2d8acbace9a74d464bb | |
| parent | a27a5aa83696200e22a459950081eb443e01e427 [diff] |
Move the mobile_install command to a separate package and module The mobile_install command has a hard dependency on the Android rules. For mu-Bazel, we're trying to build a minimally useful Bazel binary, and that should not contain the Android rules. Moving the mobile install command implementation to a separate package is one step towards that. -- PiperOrigin-RevId: 144680452 MOS_MIGRATED_REVID=144680452
{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.