| commit | b4d58a27680d84097a5d1d66ab15fdd2efb8eda6 | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Mon Aug 31 15:15:48 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon Aug 31 19:18:46 2015 +0000 |
| tree | e48c5a6b1ea6351246e7c3116ba41c0b93d2e029 | |
| parent | 70265eca3b2a12ef7d2d1949b3e3e6c2b44f26f0 [diff] |
Remove the OFFLINE coverage file constant. All the code paths to the baseline coverage action now go through the InstrumentedFilesCollector, which only passes the local sources for baseline coverage, which are only those files matching the instrumentation spec, which in turn are only files that are valid for offline coverage (in combination with the withBaselineCoverage flag). -- MOS_MIGRATED_REVID=101935566
{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.