| commit | 777b30d06700f76ba580715429f3663de3fa0529 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Feb 24 16:30:15 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Mon Feb 27 15:05:00 2017 +0000 |
| tree | d3abdc6f42d04256c486270add24e5b0c5d3abbd | |
| parent | 25aa033ad5657a5cfa16e8307464648b9374be2d [diff] |
Provide more reporting options to SkyFunctions With more specific information to be reported by Skyfunctions, e.g., to inform the build-event protocol on missing files, the EventHandler interface is no longer enough. Therefore, provide an enriched context for reporting events. -- Change-Id: I2d06166fe4d5b9054e24ad8c752fafc039e3f9f8 Reviewed-on: https://cr.bazel.build/8794 PiperOrigin-RevId: 148463437 MOS_MIGRATED_REVID=148463437
{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.