| commit | 4d900ceea12919ad62012830a95e51f9ec1a48bb | [log] [tgz] |
|---|---|---|
| author | Chi Wang <chiwang@google.com> | Fri May 27 22:46:12 2022 +0200 |
| committer | GitHub <noreply@github.com> | Fri May 27 15:46:12 2022 -0500 |
| tree | 793e672adf20afada88f8cb75094da4da5774945 | |
| parent | 07583479224ef9dcd361584b7ea8450607809c5f [diff] |
[5.2] Remote: Fix a bug that outputs of actions tagged with no-remote are u... (#15453) * Remote: Fix a bug that outputs of actions tagged with no-remote are u… …ploaded to remote cache when remote execution is enabled. Fixes https://github.com/bazelbuild/bazel/issues/14900. Also fixes an issue that action result from just remotely executed action is not saved to disk cache. The root cause is the action result is inlined in the execution response hence not downloaded through remote cache, hence not saved to disk cache. This results in the second build misses the disk cache, but it can still hit the remote cache and fill the disk cache. The third build can hit disk cache. Closes #15212. PiperOrigin-RevId: 441426469 * Fix test Co-authored-by: Chenchu K <ckolli@google.com>
{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
