| commit | 7145869bb0d6941368ef5d16c34b9e8befd08ade | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@linta.de> | Wed Jul 05 05:45:29 2017 -0400 |
| committer | John Cater <jcater@google.com> | Wed Jul 05 10:58:48 2017 -0400 |
| tree | 2138900b2d89c8bbe2c3691e926b4f946fb78f03 | |
| parent | 9582db29faa2674cf3fab26c0ac61b04db393cec [diff] |
blaze_util_freebsd.cc: gracefully handle server directory being NULL Gracefully handle the case that the working directory of the server process no longer exists in the file system. This happens if the directory in which bazel was called gets removed and later a directory with the same name is created; a particular such case is running bazel in integration tests. Closes #3324. PiperOrigin-RevId: 160938332
{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.