| commit | 704e778d46a09986b0be4ecd03b22bb69a320a86 | [log] [tgz] |
|---|---|---|
| author | Michael Staib <mstaib@google.com> | Thu Aug 27 17:44:26 2015 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Fri Aug 28 09:21:09 2015 +0000 |
| tree | a2cdf63eef3b81af2c44ed465ab1f96cdc2f5e0b | |
| parent | 9b38b2cdebc2bde00e85fc4ed8ed7bef400f6c8c [diff] |
Always create a generating action for _proguard.jar, even if no specs are specified. Because configurable attributes can be used to create an android_binary which has no proguard_specs, and because it's impossible to tell this case at the time the implicit outputs are defined, some generating action must be defined even if no proguard_specs actually make it to the rule. If the proguard_generate_mapping attribute is specified, the mapping is also generated. Both are generated by a FailAction and so are not actually produced. -- MOS_MIGRATED_REVID=101694294
{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.