| commit | b1f3302d93b05221ae7b6a50665a9765584b9edd | [log] [tgz] |
|---|---|---|
| author | Kush Chakraborty <kush@google.com> | Wed Feb 08 17:35:02 2017 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Wed Feb 08 17:51:08 2017 +0000 |
| tree | 4fde266868dae00e1ae9ac1594907144aece539b | |
| parent | 777f3afea4195e094d45bdfc317b236146117ff7 [diff] |
Make bazel test suites fail without a real test, by no longer adding an empty test in the TestSuiteBuilder. The current scenario can be bug-prone since changes to the TestSuiteBuilder code may bypass all tests, and in the absence of test failures, our tests will signal success. RELNOTES: Make it mandatory for Java test suites in bazel codebase, to contain at least one test. -- PiperOrigin-RevId: 146919833 MOS_MIGRATED_REVID=146919833
{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.