| commit | 4a303e2cd840810b95cbc793e38bdca48e6d9556 | [log] [tgz] |
|---|---|---|
| author | cushon <cushon@google.com> | Fri Apr 14 02:31:44 2017 +0200 |
| committer | Jakob Buchgraber <buchgr@google.com> | Fri Apr 14 12:40:56 2017 +0200 |
| tree | 0b2ebca38a7595ff79a26fa652647cdfa3fe0381 | |
| parent | 11789f49e26be9c9dfb225b32ea0413258a8cb8c [diff] |
Automated g4 rollback of commit b0ac3b41700cdc575c36ff2de191bc9ba2b6abf0. *** Reason for rollback *** kokoro failures were not flakes :( *** Original change description *** Fix escaping of '@' in javabuilder command lines "@" is used to denote params files, so when it appears in labels it is escaped as "@@". The second "@" should be removed during flag parsing to avoid e.g. having it show up in strict deps errors. See bazelbuild/buildtools#83 PiperOrigin-RevId: 153127997
{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.