| commit | 402d112bc25449f1e690bbbace600bbcda834d24 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Sep 24 00:21:04 2015 +0000 |
| committer | Philipp Wollermann <philwo@google.com> | Thu Sep 24 14:21:05 2015 +0000 |
| tree | 7ab138fa656c0ce80cd8fd9171891dfb7563f687 | |
| parent | 93cb6466b928eb4abd1f0bd050619a31d3752f68 [diff] |
Rollback of commit 53330510c6ea5cd6257b9981b44e52d15a9e01aa. *** Reason for rollback *** Breaks tests. *** Original change description *** Remove gen jar implicit output. This allows us to only create a jar for libraries that use annotation processing. It also increases our flexibility by reducing the visibility of these gen jars to an undocumented output group. -- MOS_MIGRATED_REVID=103800137
{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.