| commit | 48fa81a3d7678b92d0588ddd832ffdb50fd156d3 | [log] [tgz] |
|---|---|---|
| author | David Chen <dzc@google.com> | Fri Jul 29 09:05:11 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Jul 29 10:26:00 2016 +0000 |
| tree | 983657cfc689a1d5adc9d6b6f70bc586d2832b1e | |
| parent | cba16459185325284ccb4077408f764324a9afe1 [diff] |
Move designs/ directory out of docs/ and into site root. For versioning Bazel's documentation, we only want to version the pages under the Documentation portion of the site. Since Design Docs are more meant for Bazel developers and are generally not continually updated for each release, we should not version the design docs. Moving the directory for the design docs out of docs/ will also simplify the change for versioning Bazel's docs. -- MOS_MIGRATED_REVID=128788588
{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.