| commit | 74d716bf1b00badbe7f1f028d8f005b1780b06bc | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Wed Nov 23 12:38:24 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Wed Nov 23 13:56:26 2016 +0000 |
| tree | 281823450c64d35a9912e8a88967b729fdf335f7 | |
| parent | 7e5396a66cd7021150f9fab9ec8160c92fde618d [diff] |
Declare order constraint in BEP In the build event protocol, provide order guarantee to facilitate use: All the root causes referenced by a TargetCompleteEvent need to come before that event. Note that, by causality, the root causes have to be already knows, hence the root cause event is either generated already or about to be generated. -- Change-Id: I2bbe9b1a832c23217104a41e21d2f6ff13211c9a Reviewed-on: https://cr.bazel.build/7371 MOS_MIGRATED_REVID=140018440
{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.