| commit | dadde6f1bf93efa3e73dbbbf557ec37a57a0eefe | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Wed Jan 18 17:32:07 2017 +0000 |
| committer | Vladimir Moskva <vladmos@google.com> | Wed Jan 18 18:34:10 2017 +0000 |
| tree | 59c15f960773724c95962c96dbcd487d107f7bb9 | |
| parent | 227a06872dd5e1a2ca32655ad699848b3651db36 [diff] |
Support mapping of Paths to URIs Bazel-created files (like log files of test runs) are internally reported as Paths. However, this is not always the most useful representation of the location of that artifact for a consumer of build events. Therefore, support a mapping of paths to more useful URIs. -- PiperOrigin-RevId: 144843525 MOS_MIGRATED_REVID=144843525
{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.