| commit | 905a29d0e61d5393f2b7646fae8e6b4a819e68f4 | [log] [tgz] |
|---|---|---|
| author | Carmi Grushko <carmi@google.com> | Fri Dec 09 20:42:29 2016 +0000 |
| committer | John Cater <jcater@google.com> | Mon Dec 12 20:35:05 2016 +0000 |
| tree | d45abc27c5da03ab346c1bb2f07a6200a3236185 | |
| parent | 7f2d9ccbdef6e5c5a23d8f80f36464bcf1d54475 [diff] |
Names of extra-action protos now take into account aspect names. That is, if an Aspect registered an action that an extra-action is shadowing, its name will be used when creating the extra-action's ID and name. Without this change, it's impossible to analyze extra-actions when there's more than one aspected rule that acts on the same rule (e.g., java_proto_library and java_lite_proto_library on the same proto_library). -- PiperOrigin-RevId: 141587608 MOS_MIGRATED_REVID=141587608
{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.