| commit | 738e5727bab23961c7cc423606f38f8b97a8150e | [log] [tgz] |
|---|---|---|
| author | Philipp Wollermann <philwo@google.com> | Mon Feb 27 17:17:00 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Feb 28 11:31:47 2017 +0000 |
| tree | 58506febf304f6a0da49a977304ea24c22164dba | |
| parent | 4229823937ad6c6395fefd51b5f617a40d4ce46b [diff] |
sandbox should create regular empty files, not symlink to /dev/null. Adds a test based on our Python rules that makes sure that this actually fixes the issue. Thanks to @duggelz for the suggestion. It seems like our Python rules are the only place that actually provides an EmptyFilesSupplier to Runfiles, so there's probably no simpler way to test this behavior in an integration test. Fix #1458. Fix #2394. -- PiperOrigin-RevId: 148656193 MOS_MIGRATED_REVID=148656193
{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.