| commit | 0a05086f17c72a3614747b1897e95234bcb07260 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Nov 11 17:26:44 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon Nov 14 14:51:40 2016 +0000 |
| tree | 7aadd38ee828a595f7718e9f6e2d033852b2dc70 | |
| parent | fab84872276291dc8ed24e1638f743595df0e722 [diff] |
In the //:srcs completeness test, ignore derived The compile.sh script contains a test verifying that all sources of Bazel are contained in the //:srcs target. As reference, the list of files reachable from the top-level directory is taken. In this check, ignore all derived sources, i.e., the content of the derived subdirectory to make this test pass as well when executed from the distribution artifact. -- Change-Id: I590bc9f424ed5b9f87ed07166ecb75b5aeac9fb3 Reviewed-on: https://bazel-review.googlesource.com/#/c/7136 MOS_MIGRATED_REVID=138884271
{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.