| commit | a03599225c010739e9d2e852400f1fdc94f8ee91 | [log] [tgz] |
|---|---|---|
| author | Philipp Wollermann <philwo@google.com> | Thu Jul 14 15:10:10 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Thu Jul 14 17:46:04 2016 +0000 |
| tree | 6d2bf024e104b58c04ef7412ee42f7eca94959ce | |
| parent | 0e7a4171b13c9332bd278a3a9b70699af551853a [diff] |
StandaloneTestStrategy: Use relative paths for environmental variables related to tests. This allows for better caching and also makes it easy to run tests in a different directory than the global execroot. The paths are rewritten to absolute paths in test-setup.sh, because Test Encyclopedia says that we pass absolute paths to tests in these variables. -- MOS_MIGRATED_REVID=127432675
{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.