| commit | 20703c2667539202ca8fcbe93ebd9a5450c7e6ab | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon Aug 15 21:01:20 2016 +0000 |
| committer | Philipp Wollermann <philwo@google.com> | Tue Aug 16 15:21:02 2016 +0000 |
| tree | cfa3186d0430246ac5254b5e5d104cb23b78acca | |
| parent | 6c64081b212ba8ac4ea0ae16ab2e452ef2c0b873 [diff] |
Gracefully handle non existing test descriptions This change is necessary due to recent move away from Guava immutable collections (which returns null in case of non-existing item) to Java native ones (some of which throws exceptions). One such use case where it was breaking the code was tests that uses junitparam, which might be an indication of another problem. -- MOS_MIGRATED_REVID=130321230
{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.