| commit | b6f3111d8e460de35a5e5570bd784919fc30c5f8 | [log] [tgz] |
|---|---|---|
| author | Chi Wang <chiwang@google.com> | Mon Oct 24 06:54:32 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 24 06:56:17 2022 -0700 |
| tree | 096781d89e31d0f24dd4a92246cf29f074ee614b | |
| parent | 62836d4474abf9be4016c45e56a6a5858d2394b3 [diff] |
Use ToplevelArtifactsDownloader to download toplevel artifacts Previously, with `--remote_download_toplevel`, Bazel only downloads toplevel outputs during spawn execution. It has a drawback that, if the toplevel targets are changed in a following invocation, but the generating actions are not able to be executed because of skyframe/action cache, the outputs of new toplevel targets are not downloaded. `ToplevelArtifactsDownloader` fixes that issue by listening to the `TargetCompleteEvent` (which is fired every time after the toplevel target is built event if it hit the cache) and download outputs in the background. Additionally, it can listen to more events during the build hence is more flexible to define additional outputs to be downloaded as toplevel outputs. Working towards #12665. Fixes #13625. Fixes #11834. Fixes #10525. Closes #16524. PiperOrigin-RevId: 483368093 Change-Id: I2184cbbb1d54548498eaa6caa07055a9336fd97e
{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
