| commit | 56328986232dfe4d92f738ab3bbd26d89236a428 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Mon Jan 16 13:11:05 2017 +0000 |
| committer | Vladimir Moskva <vladmos@google.com> | Mon Jan 16 13:48:55 2017 +0000 |
| tree | e1a72698ef0a508b90eb303e5cb2b7602d43f283 | |
| parent | 3a7f5626976a3452427832dde0e0d1a09c57917d [diff] |
Jarjar the third-party dependencies of the Jacoco test runner. This is the second encore of commit 823091f7516abf7d854021edc765daf1467f1647. The first one failed because jarjar tried to write to C:\WINDOWS , the second one failed because cygpath doesn't work for some reason on our CI machines and I hope that the "jarjar_bin cannot found" error message was only a fluke. Otherwise, this'll be fixed online. -- PiperOrigin-RevId: 144625508 MOS_MIGRATED_REVID=144625508
{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.