| commit | a5dde12b0d945b54967969fafa4d5e40692f9a44 | [log] [tgz] |
|---|---|---|
| author | Googler <chiwang@google.com> | Thu May 04 08:59:07 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 04 09:01:45 2023 -0700 |
| tree | e54d7df89ed2e8ac95a3bd636826f876dd91d8a4 | |
| parent | d228ca0f8e7c89e321047e5f7f2722b5e8c70425 [diff] |
Download toplevel artifacts within spawn execution so that after action execution, the outputs are already downloaded. We have three types of downloads: 1. Download within spawn execution: the download is part of the spawn execution. Similar to normal build that, during the spawn execution, outputs are written to local file system. Metadata are not injected to skyframe, but instead, are calculated, e.g RegularFileArtifactValue. 2. For action that doesn't have spawn, e.g. SymlinkAction, the download is part of action finlization before injecting metadata into skyframe. 3. Download afterwards: the download is not part of the spawn execution. During spawn execution, metadata of outputs are injected into skyframe as RemoteFileArtifactValue. Dynamic execution, for example, can then request the downloads later. PiperOrigin-RevId: 529423585 Change-Id: If78663e22f0d36d621ffb35331c7ae08dc79fccd
{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
