| commit | 5b46a48db8b380ba9afe2df2cb7d564b0c927913 | [log] [tgz] |
|---|---|---|
| author | Tiago Quelhas <tjgq@google.com> | Thu Sep 29 08:45:49 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 29 08:47:07 2022 -0700 |
| tree | a79b0e495240b758fa08779a3db5cc6cb7a667cc | |
| parent | 6c78ed889183658e66702dcf83490b17b3230d46 [diff] |
Upload dangling symlinks found in the outputs of local actions. Since we don't know whether a dangling symlink is supposed to point to a file or a directory, we always report it as a symlink to a file. The distinction only matters in V2 of the protocol, with V2.1 reporting them uniformly, so it doesn't seem to be worth the effort to match up the input and output types. Dangling symlinks to absolute paths are unconditionally uploaded. A followup PR will gate their upload on the presence of the respective server capability (SymlinkAbsolutePathStrategy.ALLOW). The change is behind a new --incompatible_remote_dangling_symlinks flag, which will be introduced in the flipped state. See #16353. Progress towards #16289. Closes #16352. PiperOrigin-RevId: 477735370 Change-Id: I6210d152529e4603a49377a9e72e8e116ced6b85
{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
