| commit | 7b835d97219e40ee92b109fbecd2dc3b37db024c | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Dec 02 10:52:57 2016 +0000 |
| committer | Irina Iancu <elenairina@google.com> | Fri Dec 02 12:20:14 2016 +0000 |
| tree | 47e3d7eace3c6ab01224a8c6dd9e8342a9ae2f13 | |
| parent | 33d63516f712bc81c6c15f8348272c390b05719e [diff] |
Do not patch WORKSPACE in the release process While we do need changes for certain test to refer to a local copy of android SDKs, we do not want those changes in the environment where we build the release artefacts (in particular the distribution artefact). -- Change-Id: I471a8c23efea389f52cd7b07b8511f69d16b8d3d Reviewed-on: https://cr.bazel.build/7592 MOS_MIGRATED_REVID=140831994
{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.