| commit | 1d971c15941e91c585cf7c2124cff4e42bcdbd91 | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Mon Aug 31 08:31:51 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon Aug 31 19:13:25 2015 +0000 |
| tree | ded38e7e1e51f6eb8dacc11159f21bc3933ecbac | |
| parent | 30c6e9598367c7c35577d56422e6f00ccc9368bc [diff] |
Merge the baseline coverage code path into the coverage codepath. We're currently doing too much work for baseline coverage - every rule creates an action for its entire transitive closure; these actions are added to the output group for baseline coverage, but not transitively accumulated. It would be better for every rule to create an action for local baseline coverage, and to aggregate the baseline coverage artifacts down the dependency tree. By merging the code paths, the InstrumentedFilesCollector can perform the aggregation, because it can distinguish local and transitive files; I'm planning to implement that in a subsequent change. -- MOS_MIGRATED_REVID=101914334
{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.