commit | 0fc2ddf56225734aff4631f93031eec4b150cd67 | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Thu Jun 23 09:17:13 2016 +0000 |
committer | Lukacs Berki <lberki@google.com> | Thu Jun 23 11:10:46 2016 +0000 |
tree | 692145ceed4dea91a66a92b13788b63f3532e178 | |
parent | 5db38e7148e39a20575aa51b76620078d00ce463 [diff] |
experimental UI: after analysis summarize the work done there At the end of the analysis phase, show the amount of work done during this phase (e.g., number of packages loaded) in a way similar to the last progress message shown for loading. In this way, users will over time learn the number of packages their project depends on; thus the progress shown during loading will become more meaningful to them. -- Change-Id: If56fab5704c419be988e55f0c1705b3732c11369 Reviewed-on: https://bazel-review.googlesource.com/#/c/3872 MOS_MIGRATED_REVID=125656896
{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.