| commit | 49a797a4eba6d00739ce5bfdbdbe746a25295598 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Thu Jun 30 16:01:57 2016 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Fri Jul 01 07:10:10 2016 +0000 |
| tree | 67aabf5add30a12674b9842c9d6e5ff88b46bc37 | |
| parent | dc174c400c197983a984b2f28e64eeb66fb92c0a [diff] |
Add status information to the design documents As we also collect design documents on unimplemented designs, it is important to keep status information with our design documents. -- Change-Id: I3e08a8b05daf7a0c7f12cffbe4a8e350de5e34f8 Reviewed-on: https://bazel-review.googlesource.com/#/c/3943 MOS_MIGRATED_REVID=126307804
{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.