| commit | 5d2ae52c032203575f145ca409f2b86f1e8c700b | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Fri Feb 17 13:47:44 2017 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Fri Feb 17 14:56:31 2017 +0000 |
| tree | 8c3117a69b722790075a10fca1b702e2d89630c1 | |
| parent | 3b6370ced0de326b34a89db2ce13bcdfa276bbc5 [diff] |
Move FileAccessException to the vfs package It was previously in unix, but also used from non-unix file systems, which means it's not actually unix-specific. This is in preparation for splitting compilation of the unix and windows file systems into separate libraries. That improves layering and reduces compile times - note that Bazel already injects the vfs into its lower layers, which should only rely on the normal vfs APIs, not on anything platform-specific. -- PiperOrigin-RevId: 147829659 MOS_MIGRATED_REVID=147829659
{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.