| commit | 003f7664c91f4fec81e7607c0b59651915836d3a | [log] [tgz] |
|---|---|---|
| author | adgar <adgar@google.com> | Tue Jul 28 08:55:02 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 28 08:57:32 2020 -0700 |
| tree | cfa038e0ed9b64236d76013135eedf5b9d19e625 | |
| parent | 53e22d924c324a3e3944e2d1fca5d3eb285ab9b5 [diff] |
Failed target/aspect completions include resolved artifact paths in BEP. The implementation of feature request #9413 adds artifact URIs to BEP for action groups that succeeded within an overall failed build (see commit ecd2a57662). These artifact URIs were passed to the BES subsystem as local paths and bazel relied on BES's artifact upload facility (which substitutes a remote URI after upload) to make the artifacts available to other users. With the introduction of "build without the bytes" functionality, in particular the `--experimental_remote_download_outputs=minimal` setting, an artifact from a successful action group may not be downloaded to the local filesystem. For targets that succeed, the local path is converted to the remote URI *before* it is passed to the BES subsystem which knows not to attempt an upload. Failed targets were still passing an (erroneous) local path to BES, which would crash when it attempted upload. This change ensures failed targets whose artifacts have known remote URIs pass those remote URIs to BES, which knows not to attempt an upload. Fixes #11764. PiperOrigin-RevId: 323581170
{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:
See CONTRIBUTING.md
