| commit | 34eda0287b77aaf0314c7fdec4fc2c26e65f787e | [log] [tgz] |
|---|---|---|
| author | Janak Ramakrishnan <janakr@janakr-macbookair2.roam.corp.google.com> | Mon Jul 27 15:43:40 2015 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jul 27 16:34:45 2015 +0000 |
| tree | 84e936efe3db12fe18ace2a8ea755a971dd13fc3 | |
| parent | eff6de9d9865229f095ebfc714754145db08d3e7 [diff] |
Disallow non-empty dotd files that do not end in a newline. Such files likely arise from corrupted filesystems, and an error about the file format is more useful to the user than mysterious one about undeclared inclusions coming from truncated file names. -- Change-Id: I8be4bd3cd4e1845d2904a91e99aeafc41b3b9d8c Reviewed-on: https://bazel-review.googlesource.com/1660 MOS_MIGRATED_REVID=99182205
{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.