| commit | 94261751bf2babe093696c35208e09768e3fd05e | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Fri Mar 31 20:05:26 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Mon Apr 03 13:37:16 2017 +0200 |
| tree | 6ba6ff401e0442d43f611db22b1a9ec84b0983e7 | |
| parent | be5f25ca01d443193a97dae99ff4d1e90311bdaf [diff] |
Add --all_incompatible_changes, the user's shorthand for turning on all --incompatible_* flags Note that if a developer adds a poorly-formatted incompatible change @Option, constructing an OptionsParser will now fail with an unchecked exception. This can cause some unit tests to fail in unexpected ways, but the developer should see an appropriate error message when the server starts up. To be added: A separate integration test that ensures the expansions of --all_incompatible_changes don't clobber each other. RELNOTES: None PiperOrigin-RevId: 151858287
{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.