| commit | f368e0411d152454c3c57a061597c8b60a1fb888 | [log] [tgz] |
|---|---|---|
| author | David Chen <dzc@google.com> | Tue Dec 15 17:36:24 2015 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Wed Dec 16 11:38:32 2015 +0000 |
| tree | 62f9ec703adad4061fe2545a077ca36349a1979f | |
| parent | 01691331fbc51f82dbc5a88796aea4fe215c899c [diff] |
Refactor BuildEncyclopediaProcessor to use a common RuleFamily class for rule documentation passed to templates. * This simplifies the logic in BuildEncyclopediaProcessor, reducing the number of various different data structures we use for generating different pages. * This also makes RuleFamily more similar to the BuildLanguage proto, which we we may consider using in the future for the native rule docgen since the Skylark docgen will be using BuildLanguage. -- MOS_MIGRATED_REVID=110265727
{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.