| commit | 4409652fb780677f8e8e431c6da5a08d9ed245f2 | [log] [tgz] |
|---|---|---|
| author | Philipp Wollermann <philwo@google.com> | Thu Jun 30 11:56:14 2016 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Fri Jul 01 07:06:13 2016 +0000 |
| tree | 0995885fb3cba054fbe38d9f2043da30b30f8723 | |
| parent | a18add1613574a15c81f60bde847c5d7b2bedcb5 [diff] |
Add a javac_supports_workers attribute to the java_toolchain rule. If this is set to true (which it is by default), JavaCompilationHelper will set the "supports-workers" tag on the execution info for the Javac SpawnAction. If it is explicitly set to false, this tag will be absent. In a follow-up CL, the WorkerSpawnStrategy will check whether this tag is present and fallback to non-worker execution if not. This is needed to safely enable workers by default in Bazel without breaking the older JDK7 JavaBuilder, which does not support workers yet. -- MOS_MIGRATED_REVID=126290991
{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.