| commit | b8b4a1c0fa248d50eb954b5196381fd7b9ba3e06 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Wed Mar 23 13:06:41 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Mar 23 14:43:24 2016 +0000 |
| tree | 444c28540cd479959ca77f9b8e7330c2f9291720 | |
| parent | 2b8ae5b58ae03a0e90a19cf966e0467e8c7dac59 [diff] |
Register the primary handler with the event bus If bazel is invoked with --color=no, two event handlers are in use simultaneously, using different output streams. For the event bus, register the one that is aware of ansi control characters, as this is the one that will also pass through stdout/stderr events. -- Change-Id: I83f1164b9057cebf9345c315f42c8d54a88d3888 Reviewed-on: https://bazel-review.googlesource.com/#/c/3121 MOS_MIGRATED_REVID=117922780
{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.