| commit | 8e138f9ffa098273823b4fe59e910de463801775 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Mon Aug 29 12:56:13 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Mon Aug 29 13:00:35 2016 +0000 |
| tree | c30264c2f0c91279963a80ab74d302ba82dace92 | |
| parent | d0d6cf7f2a88624e443a7f5e50e21e6653f73d3e [diff] |
Fix typo in shell variable names site/jekyll-tree.sh derives their own variables TMP and OUT_DIR from TMPDIR (using /tmp as a default, but not touching the TMPDIR variable). So those variables ought to be used also in the rest of the script. -- Change-Id: Ic62dffd36347982a34bc7c5cbabc7c9b3ada0cb7 Reviewed-on: https://bazel-review.googlesource.com/#/c/5671 MOS_MIGRATED_REVID=131583456
{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.