| commit | 7af1c3394766af41bd990322b1c52507cd6b78de | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Feb 26 11:32:01 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Sun Feb 28 17:04:14 2016 +0000 |
| tree | 93ebea26e685204b9e3e843abd9a1026d532d525 | |
| parent | cff5c43c9cb9d63efe38d2e77dae4c5655a53feb [diff] |
experimental UI: only refresh progress bar if needed The handle(Event event) method of the ExperimentalEventHandler does not produce UI changes for every event observed. Still, it used to clear and re-add the progress bar unconditionally. Move those operations into the individual cases that do produce output, so that in the ignored events nothing is sent to the terminal. -- Change-Id: I31fd8df0ee2feeb53b6686fe7350848be2a53b6a Reviewed-on: https://bazel-review.googlesource.com/#/c/3025 MOS_MIGRATED_REVID=115656142
{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.