| commit | f39dc6fc707cca9496d5baef5549bb7c24933776 | [log] [tgz] |
|---|---|---|
| author | ccalvarin <ccalvarin@google.com> | Fri Jun 09 11:51:45 2017 -0400 |
| committer | John Cater <jcater@google.com> | Fri Jun 09 14:06:16 2017 -0400 |
| tree | f5a1ad175daf54395789d19a8d33c890ca3aff9d | |
| parent | 6c1106b1a721516d3b3db54d2e1c31b44a76fbb1 [diff] |
Move InvocationPolicy to the options parser package. It was originally included in runtime due to external dependencies, and a desire to keep the options parser a general options library. These dependencies have been or will be removed, and there are plenty of other general flag libraries. InvocationPolicy is fundamentally acting on the properties of this specific OptionsParser and needs proper access to it for the proper solution to a number of existing bugs, which means having access to things that should be package private. PiperOrigin-RevId: 158523111
{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.