[9.2.0] Exclude repos with cross-repo symlinks from the remote repo contents cache (https://github.com/bazelbuild/bazel/pull/30161) (#30190) ### Description This is meant as a temporary stopgap for the many symlink-related issues found with the remote repo contents cache and includes tests found while debugging #30149. The new and old tests are parameterized in a test suite variable to keep the diff small and enable future experimentation with improved symlink support. As part of #30160, I'll investigate a more conceptual approach to symlink resolution that unifies the logic with that in RemoteActionFileSystem. ### Motivation Fixes #30149 ### Build API Changes No ### Checklist - [x] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes RELNOTES: The remote repo contents cache no longer caches or restores repos with cross-repo symlinks, thus avoiding a large surface area for bugs. The effort to reenable this support is tracked by https://github.com/bazelbuild/bazel/issues/30160. Closes #30161. PiperOrigin-RevId: 944468477 Change-Id: I4a435beaadb7c2df3e11acd910814736d2fb32c0 Commit https://github.com/bazelbuild/bazel/commit/e65fe06b2b5529f17b58a846c28512b239984628 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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
