| commit | 0b1babd65c07f2759a34f9f3f58745fe7493407c | [log] [tgz] |
|---|---|---|
| author | Adam Michael <ajmichael@google.com> | Thu Oct 27 20:27:36 2016 +0000 |
| committer | John Cater <jcater@google.com> | Fri Oct 28 16:02:45 2016 +0000 |
| tree | a10c51292eadde7bb9ee0d7370aaac948523c838 | |
| parent | 578a5122cc4bf6239222226adfa2dafd32c4c220 [diff] |
Switch default --apk_signing_method from legacy_v1 to v1. Also makes apksigner a mandatory attribute of android_sdk. Now Android builds will default to using the Apk Signer tool to sign APKs. A followup changelist will remove the legacy code path. RELNOTES: --apk_signing_method default changed to v1. Android APKs are now signed with the new ApkSignerTool by default. -- MOS_MIGRATED_REVID=137433061
{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.