| commit | 8594de82e367fb463f2d02d3adda25fc99de9a9f | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Mon Mar 20 16:30:11 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Mar 21 12:49:29 2017 +0000 |
| tree | 70e2f4234486ac3a228ece8a70a260f0d02915f2 | |
| parent | 1d7108814e9f1fd68dbbb92325779b4d5e4d0a91 [diff] |
Rationalize null-ness checks in Runfiles This now also checks symlink maps for null pointers, which it previously did not. Unfortunately, there's still one case where we add a null target to Runfiles (to represent an empty file) - this happens in Runfiles itself, and this change prevents any callers from doing so. -- PiperOrigin-RevId: 150634481 MOS_MIGRATED_REVID=150634481
{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.