| commit | e11775c2394fc48ac7fe5b632b47ae952dd552b4 | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Tue Apr 04 22:16:32 2017 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Apr 05 15:19:49 2017 +0200 |
| tree | f2426469fc4e65a6a49dcf0b6e1cddef03e0c04b | |
| parent | 8b5e0a36fda5bfc7e861e9696c2ff8f73f52679c [diff] |
Add integration test for --all_incompatible_changes flag conflicts This adds a new warning when the same flag is expanded to by multiple expansion flags. This extends an existing suite of warnings, e.g. for when an expansion flag conflicts with an explicit option. The blaze canonicalize-flags command now takes a new flag --show_warnings. This flag causes any warnings encountered while parsing the given command line to be printed to stderr. RELNOTES: blaze canonicalize-flags now takes a --show_warnings flag PiperOrigin-RevId: 152186672
{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.