| commit | a49f02536ef62ddf6ef5a17b0f7c1a35aaf81098 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Wed Mar 02 15:48:40 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Wed Mar 02 17:55:33 2016 +0000 |
| tree | bb2f895e5482c33b420dccf2f04821edc7cd6c4a | |
| parent | 028fe872c4b256875b2393019e39906b8304ff76 [diff] |
FancyTerminalEventHandler: manually break lines in progress bar Manually break lines in the progress bar (and only in the progress bar!) that are longer than the terminal width. In this way, we avoid any confusion about when the terminal advances a line; in particular, when the terminal is wider than we believe, we do not erase back into the scrollback buffer. -- Change-Id: I19f21bdbd6e6af4665d1e712b921f1a15c7d901c Reviewed-on: https://bazel-review.googlesource.com/#/c/3041 MOS_MIGRATED_REVID=116138487
{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.