| commit | 0e7a4171b13c9332bd278a3a9b70699af551853a | [log] [tgz] |
|---|---|---|
| author | Carmi Grushko <carmi@google.com> | Thu Jul 14 14:54:27 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Thu Jul 14 17:46:01 2016 +0000 |
| tree | ecfab73683394d9f92a2da0c5fad62cf0c0c2f30 | |
| parent | 26ba23e465aad365138006b906431a865c5766cc [diff] |
Rollback of commit 80d1e16b7ae1d04fa2fa4c561588fe9fdbaefc41. *** Reason for rollback *** Breaks Bazel's CI because the current release (0.3.0) is used to query some targets, which doesn't have java_proto_library yet. *** Original change description *** Use the native java_proto_library instead of the macro defined in genproto.bzl. -- MOS_MIGRATED_REVID=127431334
{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.