| commit | 8c439a094b3034f7f8ce1d335eef613fb02dfa7e | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Sep 30 10:36:41 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 30 10:37:49 2022 -0700 |
| tree | 20d071aba1694c8aa92d5548a61227483d0dd9af | |
| parent | 77e5b26ce8b02ccb6e642c496678b348c6cda064 [diff] |
Add exec platform and properties to verbose_explanation I was puzzled why a certain build was being rebuilt from scratch when I targeted a remote build system, even though the build had been completed in the local cache. Running bazel build //path/to/my/build --explain=explain.txt --verbose_explanations showed the exact same output for remote and local. Turns out, the execution platform and properties contribute to the action cache key. However, if these are not shown in the verbose explain output, this is not clear. By printing this out, it should be more apparent why the action cache key miss occurs. PiperOrigin-RevId: 478027092 Change-Id: Ie66e339b9b3a618defc2ad869f6bffa175e7f0e2
{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
