commit | f99a0543f8d97339d32075c7176b79f35be84606 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Fri Oct 07 04:26:43 2016 +0000 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Oct 07 08:11:08 2016 +0000 |
tree | 15572c936a909c763389b42b91b6c975e4ddd54f | |
parent | 0e9a1b2d51f9e03f4493e52d23cb3efc568be59f [diff] |
Rollback of commit 0e9a1b2d51f9e03f4493e52d23cb3efc568be59f. *** Reason for rollback *** [] hasn't released unknown commit yet. We need to keep the old behavior until then. *** Original change description *** Stop consulting the environment for "originating user" information. -- MOS_MIGRATED_REVID=135441115
{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.