| commit | 68f94a1d6f2eede5552fd52986a74b6e9ecaa1b6 | [log] [tgz] |
|---|---|---|
| author | Googler <jingwen@google.com> | Thu Oct 24 08:47:00 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 24 08:48:32 2024 -0700 |
| tree | c3f1bfa69b0c1a1869d33a125bc78e7a9a88d6d2 | |
| parent | 8d0e66b1c73aacbf835039b785e4242d8c604b94 [diff] |
Enable analysis caching codepaths only for commands that execute actions. For example, this includes `test` and `build`, but does not include `cquery`. This prevents the use case where the someone adds `build --experimental_remote_analysis_cache_mode=download` by default into their bazelrc, and runs a cquery command (which, WAI, picks up the flag, because `CqueryCommand` inherits options from `TestCommand`, which inherits from `BuildCommand`), and fails to this cryptic error: ``` $ bazel cquery 'somepath(//foo, //bar)' ERROR: Failed to find PROJECT.scl file for: [//foo:foo, //bar:bar] INFO: Elapsed time: 0.078s ERROR: Build did NOT complete successfully ``` It also doesn't make sense to support analysis caching with cquery anyway, because correct results require a complete, unpruned analysis graph. Same goes for `aquery`. PiperOrigin-RevId: 689397164 Change-Id: Ib63ab41450b84e782d69e148196b2bfa6413e65f
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
