| commit | c7e51046dc8cc250a304303edc28c0b4f6aaf776 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue May 03 16:24:19 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Tue May 03 21:32:16 2016 +0000 |
| tree | 2e2365a98d74cd803aee7ca3ff8684a07678e9a9 | |
| parent | d50f7b81b6ac292791715d302fa6cc9326d68475 [diff] |
4.7 of 5: Remove serialization of transitive dependencies. Serializer no longer serializes transitive resources. That turned out to be a performance issue with large trees. Instead,it relies on the build tool to indicate the direct and transitive resources. This reduces the number of keys that get pulled from diamond dependencies and stays much, much leaner. -- MOS_MIGRATED_REVID=121382705
{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.