| commit | 1f02a434a42cb7ce2cbdad8592709ad518772eb7 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Thu Nov 26 10:12:49 2015 +0000 |
| committer | Philipp Wollermann <philwo@google.com> | Thu Nov 26 13:19:47 2015 +0000 |
| tree | f26143ce38752a7591dd7fe09af759d9c7edd2ab | |
| parent | 7b599453389b3a00eebf25c58cde322a0e7bdf02 [diff] |
This change fixes a mysterious timeout when the Maven tests fail. I have no idea why this is a problem: apparently, postincrement fails (but only the first one, so theoretically, changing only that line would be enough), preincrement works and i=$(( $i + 1 )) also works. The documentation of bash is of no help, I checked the file on the off chance that there are weird Unicode characters on that line (or where i is set) and I had no more ideas after (other than there being a bug in bash) -- MOS_MIGRATED_REVID=108774915
{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.