| commit | 19fde1fc26d261fa95e115c3a0bfb0bd92f1e13a | [log] [tgz] |
|---|---|---|
| author | Janak Ramakrishnan <janakr@google.com> | Mon May 23 21:20:16 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue May 24 11:58:05 2016 +0000 |
| tree | 6daec251962eb8d867413ec31e4b97997c96daca | |
| parent | a3b8f3586f38ccb1dd2197390813514ffccec44a [diff] |
Separate killing Bazel on OOM using -XX:OnOutOfMemoryError and pessimistically OOMing when GC thrashing. The first seems to make us hang on OOM, which is kind of the opposite of what we want. These flags are now even more terribly named than they used to be, but a rename can wait until we actually know what we want. -- MOS_MIGRATED_REVID=123036704
{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.