| commit | 0b9ebfee8d7f3bd5cf68f4dba4790bf3fed9349d | [log] [tgz] |
|---|---|---|
| author | Adam Michael <ajmichael@google.com> | Wed Dec 14 22:58:39 2016 +0000 |
| committer | John Cater <jcater@google.com> | Thu Dec 15 20:36:45 2016 +0000 |
| tree | 30beb455d497083a463fa866dd1f6ad9575fd26e | |
| parent | e2beb245e6e962acb2690c5e0234cedcc5046523 [diff] |
Rollback of commit 27cd7f6bb4a02f56f9ad73e57e71e69a1c00d5ea. *** Reason for rollback *** Rolling forward, intentionally breaking loading phase (and therefore `bazel fetch`) for android_binary in Bazel if no android_sdk_repository is set up. Will not submit until Tensorflow's use case is cleaned up in https://github.com/tensorflow/tensorflow/pull/6225. -- PiperOrigin-RevId: 142068703 MOS_MIGRATED_REVID=142068703
{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.