| commit | 70c5790e4fb01db382d61d457596a46b68ba8d13 | [log] [tgz] |
|---|---|---|
| author | Janak Ramakrishnan <janakr@google.com> | Thu Mar 10 00:58:59 2016 +0000 |
| committer | David Chen <dzc@google.com> | Thu Mar 10 10:23:47 2016 +0000 |
| tree | 501e10f31d9acc339d8f27a9e35a220b51b43090 | |
| parent | be7176811f77dd58de763c7ac24d5fb7f849c5c0 [diff] |
When --experimental_oom_more_eagerly is enabled, tell Bazel to exit with an OutOfMemoryError and have the JVM send Bazel a SIGUSR2 when it detects an OOM. This should help in certain pathological cases when Bazel GC thrashes for some time after an OOM has been detected. -- MOS_MIGRATED_REVID=116819359
{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.