| commit | eeb89700bd859635b79c8beee449960563eea16c | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Thu Apr 13 10:10:43 2017 +0000 |
| committer | Jakob Buchgraber <buchgr@google.com> | Thu Apr 13 12:50:31 2017 +0200 |
| tree | 84ba433c8521cb75dff41188940999aba913d9f3 | |
| parent | f85290973eaafa10d031a092ed795a7fd8165533 [diff] |
BEP: for local transports optionally drop path conversion For transports that are purely local (like the ones writing to a local file), it sometimes can be useful to skip path conversion and use the local paths directly. Support this for the text and binary format file transports. Change-Id: I2ac2e187ebb11ff82c4e1ddf4881ea54f9d4205d PiperOrigin-RevId: 153044267
{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.