commit | b776d6c12e952eb358c1a036cc9d93d8944c4c77 | [log] [tgz] |
---|---|---|
author | Nathan Harmata <nharmata@google.com> | Fri Oct 14 22:38:17 2016 +0000 |
committer | Philipp Wollermann <philwo@google.com> | Mon Oct 17 11:19:17 2016 +0000 |
tree | 0f0381870fddf2bae3d63e48af61c1e69592b6e0 | |
parent | 29cc0d9c54ec8d4b80d63824783ba3da2abed1a6 [diff] |
Rollback of commit 0c7a42a09d85ddffd9b860bcb31e4c43a00632c1. *** Reason for rollback *** [] *** Original change description *** Slight refactor of ExternalFilesHelper: -Make FileType and ExternalFileAction public. -Have producers use ExternalFileAction, rather than a boolean, to specify the desired behavior. And a big change in semantics (doesn't affect Bazel): -Replace ExternalFileAction.ERROR_OUT with ExternalFileAction.ASSUME_NON_EXISTENT_AND_IMMUTABLE, which does what it sounds like. This new action, like the old ERROR_OUT, is _not_ used in Bazel. -- MOS_MIGRATED_REVID=136206810
{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.