| commit | 617bb896dc5d2b815449459e991c577237d7a7fc | [log] [tgz] |
|---|---|---|
| author | aehlig <aehlig@google.com> | Tue Apr 04 15:03:23 2017 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Apr 04 18:39:53 2017 +0200 |
| tree | e25a4bfe6e925ad2cff32c71447af412a77faf2e | |
| parent | 0297702d9533142e6c326660f913899d25b89b5d [diff] |
BEP: provide events a generic converter class Change the BuildEvent interface to accept a generic class of converters. In this way, we won't have to change it again in the future, once more converters are needed. In fact, a new converter is needed right now (will be added in a follow-up patch) to allow build events to know the name of named artifact groups already reported in the stream. Change-Id: Ibb32ea5fff361e21bcf2d34818d8351a1da7a2e3 PiperOrigin-RevId: 152131870
{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.