| commit | 2707a886681e14fc22edca4c6c4bccca12018083 | [log] [tgz] |
|---|---|---|
| author | Michael Staib <mstaib@google.com> | Fri Sep 16 21:06:40 2016 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Mon Sep 19 07:35:12 2016 +0000 |
| tree | 9cd4e2e596c26e685f474c7fb6a4fcf9291a91e6 | |
| parent | 8618b9d67d20a737908113fa89357ac321a9669b [diff] |
Enable aspect invocations to be matched by output filters. Currently aspects have no tag, i.e., they don't get checked against output filters at all. This changes aspects to have a tag of the same form as the rule they are attached to (i.e., the label of the target). Since the default output filters match on ^//package[:/], this should cover most uses of the output filter, while still allowing for finer control for those who crave it. -- MOS_MIGRATED_REVID=133425215
{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.