| commit | 27762e2207d2ea817499756298f08c715790d187 | [log] [tgz] |
|---|---|---|
| author | ulfjack <ulfjack@google.com> | Tue Jul 04 06:01:11 2017 -0400 |
| committer | John Cater <jcater@google.com> | Wed Jul 05 10:57:53 2017 -0400 |
| tree | 604382da8d38f7f2f8459aa7614e050124f80e8e | |
| parent | 9409109c3016c51403ed4387ecda6c99459f1a8d [diff] |
Add an on-disk storage option for the remote worker I'm planning to switch the remote worker over to the on-disk storage system, and delete the in-memory option. Currently, running a Bazel build with the in-memory storage system uses up over 50% of the total available memory on my machine (I only have 32 GB total), and grinds it to a complete halt (unless I close most of my apps) on a simple build of //src:bazel. PiperOrigin-RevId: 160877546
{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.