| commit | fb64609c3f1d3492f4d80807f5d91894fa147172 | [log] [tgz] |
|---|---|---|
| author | Jakob Buchgraber <buchgr@google.com> | Mon Feb 27 18:53:25 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Feb 28 11:32:42 2017 +0000 |
| tree | 512a58c41dee774ad2694db30883643fdef996dc | |
| parent | a6090926b7ae504d82f78e6fe705f454b3216cb5 [diff] |
BEP: Add tags and output files to TargetComplete event A target's tags and output files are reported as part of the TargetComplete event of the build event protocol (BEP). The output files are grouped by their corresponding output group. If an output file belongs to more than one output group it appears once in each output group. -- Change-Id: Ia37db68709850d8550e478dcc30064dc7366bd1b Reviewed-on: https://cr.bazel.build/8955 PiperOrigin-RevId: 148667599 MOS_MIGRATED_REVID=148667599
{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.