| commit | 97e79cc5773835c199ff8eefd29379bc64ab59a4 | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Wed Jan 25 12:46:33 2017 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Wed Jan 25 13:05:43 2017 +0000 |
| tree | 2a94dc2d92a87277ee661057a38564988f03b7b3 | |
| parent | fba5477499120d0d43012dccd00698ece8f5c950 [diff] |
Rollback of commit 32f033328abdd00cbec149edd87bde34095bccbc. *** Reason for rollback *** This change is no longer needed because commit d9a7d3a789be559bd6972208af21adae871d7a44 is rollbacked *** Original change description *** Add --manifest_file option into BazelJavaBuilder Now Bazel JavaBuilder can specifiy a file as the manifest file, before this it just creates the manifest file on the fly. -- PiperOrigin-RevId: 145534408 MOS_MIGRATED_REVID=145534408
{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.