| commit | e855a26691daeac81c1e823ad65c7707062e0bd2 | [log] [tgz] |
|---|---|---|
| author | Chi Wang <chiwang@google.com> | Mon Sep 13 23:50:55 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 13 23:52:09 2021 -0700 |
| tree | 5b15d1b682823519378fc18e161209c07d110bbb | |
| parent | 4b3ed3bd04084dd455aea42f206a9e917ed6dbc0 [diff] |
Remote: Update BEP uploader to use RemoteCache and more robust to upload errors Local files referenced by build events are uploaded to remote cache with `ByteStreamBuildEventArtifactUploader` which uses `ByteStreamUploader` and `MissingDigestsFinder` internally. This PR changes `ByteStreamBuildEventArtifactUploader` to use `RemoteCache` directly in order to benefit from recently improvements to `RemoteCache`. Upload error that used to crash Bazel or cause a non-zero exit code is now caught and reported. Fixes #13920. Related #11473. Closes #13959. PiperOrigin-RevId: 396526152
{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
