| commit | 07fbeaea1d7759e3c03def5ccc031a70f4218ae6 | [log] [tgz] |
|---|---|---|
| author | laszlocsomor <laszlocsomor@google.com> | Mon Apr 10 14:32:07 2017 +0000 |
| committer | Jakob Buchgraber <buchgr@google.com> | Tue Apr 11 10:49:42 2017 +0200 |
| tree | 3aade8cfa1332870cfa759b433e0a859071b985f | |
| parent | c781f45de27afe3a90dcadb5075dc90df8105d80 [diff] |
cc_configure: stricter error checks in _execute Add stricter error checks in hopes of catching occasional CI flakiness where the stdout of a command seems to get lost. It's now an error if the command returns a non-zero exit code (or a zero one if it's expected to fail) or if its stdout is empty. Previously we only checked if stderr was empty to consider the action successful. See https://github.com/bazelbuild/bazel/issues/2675 RELNOTES: none PiperOrigin-RevId: 152685220
{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.