| commit | 15c09dd1b5dbd7e76fe42d193a79dab8bfc24abc | [log] [tgz] |
|---|---|---|
| author | David Chen <dzc@google.com> | Mon Aug 29 08:56:37 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Mon Aug 29 09:42:52 2016 +0000 |
| tree | e6df9943f0f96c095a6f91240a8f4bc3a84708d9 | |
| parent | 6f2e6fb1eff1a7a265778abf1eb32a850765599e [diff] |
Replace doc pages with redirects to versioned doc pages. * Add a new `redirect` Jekyll layout. * Replace all pages under docs/ with redirects to corresponding page under versions/master/. * Prepend links on Documentation sidebar, including generated navs for the Skylark Library and Build Encyclopedia, with prefix for versioned directory. * Add code to both the internal jekyll-config.sh and external jekyll-tree.sh to add redirect pages for the Skylark Library and Build Encyclopedia. * Bring the branched User Manual doc up to date with latest changes. -- MOS_MIGRATED_REVID=131568800
{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.
