| commit | 915dbdf187d52fda5547b5336e21339dceeb8e37 | [log] [tgz] |
|---|---|---|
| author | David Chen <dzc@google.com> | Mon Aug 29 10:25:17 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Mon Aug 29 12:59:49 2016 +0000 |
| tree | cdf8f59e41abdd7cebfd1dab55c70aed26bad493 | |
| parent | 3bae1defc1d6198a7d73a616e2c448011250782d [diff] |
Implement generating single-page Build Encyclopedia. * Adds a --single_page flag to the BE docgen for generating a single-page version of the Build Encyclopedia. * Refactor BuildEncyclopediaProcessor common logic into a base class and add subclasses for generating single- and multi-page BE respectively. * Enable RuleLinkExpander to expand rule references to single-page hrefs (headings on the current page). * Update docgen velocity templates to use RuleLinkExpander to ensure links are correct on both single- and multi-page versions of the BE. -- MOS_MIGRATED_REVID=131574793
{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.