| commit | 391d67ca07c15b2383e14c6bbeefd42149361626 | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Fri Sep 18 13:41:27 2015 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Sep 21 08:57:16 2015 +0000 |
| tree | 7d05d66763cab2ed43b7ed53e74f9218aa3c4e49 | |
| parent | 47bc68df7d2b4d59075a0cc219b24bf9f902215b [diff] |
Partially revert change to collect baseline coverage from individual libraries. We still want to do that, but not like this. Our infrastructure supports per-target coverage, and so we also need to support per-target baseline coverage. I'm working on better documentation (not hard to be better than no docs), which will cover this. I left a couple of TODOs to explain how we want to do it in the future. -- MOS_MIGRATED_REVID=103379710
{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.