| commit | 3e37b6b68373b40308d6728ab3fab3b68d57814e | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Aug 06 11:07:27 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 06 11:09:13 2020 -0700 |
| tree | 2ade8992a0b0b9ae99387e4ec124325f8b73c773 | |
| parent | 41303330994072af6ff4a304c1acc205c31e994b [diff] |
Clarify --instrumentation_filter documentation This mostly changes "[a rule's] source files" to "the source files it processes" to be clear that we're talking about files belonging to the rule whose actions process those files, not the rule which _directly depends_ on the source file. That's how --instrumentation_filter works because it lines up the "should you do something for coverage with these files at build time" logic and the "should you include these files in the manifest of instrumented files" logic. Wrapping a set of source files in a filegroup rule or similar doesn't change coverage semantics. Related documentation about coverage_common.source_attributes is similarly updated. RELNOTES: None. PiperOrigin-RevId: 325267991
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
