| commit | 8a3cc9bb48026184b0c937f0ce7e37ab04621036 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Thu Jun 29 11:16:32 2017 +0200 |
| committer | Marcel Hlopko <hlopko@google.com> | Thu Jun 29 11:56:15 2017 +0200 |
| tree | 80e70a6a821cfc7932fc2a0940d98dd46ecd18ea | |
| parent | 6a8a174bd09e8f124397db10f85cc22a510a782c [diff] |
Add a test verifying that --action_env triggers a rerun of tests Issue #3265 went unnoticed for a long time, till it was fixed as a sideeffect of d1c5329ba622b29afd3ab9f670fa17064d493bc0. To avoid that happing in the future, add a test. Closes #3265. Change-Id: Ie22a1d4a2f09fd3dcadcbd900795b3e12b7dc461 PiperOrigin-RevId: 160502516
{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.