| commit | 00d479c3a51cca9362e4866864958a84ace62824 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Mar 04 12:18:56 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Mar 04 16:16:44 2016 +0000 |
| tree | fb0781089edaf2ea031f4d3eba27063afb28d17e | |
| parent | 59196361873dba1083f7ec14d2dd61c34688c9bb [diff] |
experimental UI: also remember the currently running actions By not only having a unique identifier for each running action, but also remembering additional information about the actions, in particular the action itself, we can provide a more meaningful description of the currently running actions in the progress bar. -- Change-Id: I34760a437bf731f057162ca4d08368fe35d4bc71 Reviewed-on: https://bazel-review.googlesource.com/#/c/3045 MOS_MIGRATED_REVID=116349484
{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.