| commit | 39e5a46294de31baa0411f6a59119427c66305da | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Tue Dec 20 10:58:17 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Tue Dec 20 11:07:10 2016 +0000 |
| tree | 90aaf7e33e5e547508e032a6c652635daf7164b1 | |
| parent | d40c78a98e2b1f562170396f94bf54d17c6958d0 [diff] |
Fix cycle in dependency graph during bootstrap This cycle was due to JacocoCoverage_deploy.jar being an implicit dependency of java_binary. We do not need the binary during bootstrap because we are not running with coverage but we need the target. Simply move it to exists as a java_import in tools/jdk. Fixes #2269. To be cherry-picked for #2246. -- Change-Id: I63aee0e76b305833ac0c0c2cae5abe1cbad5e6d1 Reviewed-on: https://cr.bazel.build/8036 PiperOrigin-RevId: 142537244 MOS_MIGRATED_REVID=142537244
{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.