| commit | 8e1130f625d642619f929ebac4ebb277bdf0f05b | [log] [tgz] |
|---|---|---|
| author | Liam Miller-Cushon <cushon@google.com> | Wed Jul 13 20:43:48 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Thu Jul 14 11:12:54 2016 +0000 |
| tree | 0c217ef4cd8f17ca04b6cab5289b9860fa2fbd76 | |
| parent | 303b687622bd16e5dec72ad4f503047ae91f45ba [diff] |
Allow SpawnActions to always use a params file and use it to work around an analysis performance regression caused by header compilation. SpawnAction expands the full argument list and compares the length to --min_param_file_size when deciding whether to use a params file, and header compilation actions often have very long JoinExecPathsArg fragemnts that are expensive to expand. -- MOS_MIGRATED_REVID=127354241
{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.