| commit | ea34e1825c6e45ceb2bada51c1a9de0bbf872720 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Mon Oct 28 03:26:31 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 28 03:28:02 2024 -0700 |
| tree | 54d2068fac0f0005a8e92736f6eaa13ec5679065 | |
| parent | fc27990feb62d9e64f6ce41955dc3245dc26ef2d [diff] |
Use non-snapshotted paths when creating a runfiles symlink tree. It has been a long-standing feature of runfiles symlink trees that they reflect changes made to files referenced in them after the tree has been built. In certain scenarios (currently only at Google), the FileSystem implementation may rewrite symlink target paths to point to read-only snapshots, which breaks this feature when using in-process symlink creation. With this change, the rewriting is bypassed in this case. Also improve the documentation for the BlazeModule getFileSystem() and getFileSystemForBuildArtifacts() methods. PiperOrigin-RevId: 690541050 Change-Id: I140cc68ca1b9236e9fb4049830cc3b5629eaf770
{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
