commit | dfccbf975358da93a5ef0fe0f9438873e2a06ee5 | [log] [tgz] |
---|---|---|
author | Googler <tjgq@google.com> | Wed Oct 19 12:15:58 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 19 12:17:24 2022 -0700 |
tree | 246370fcc25fa4ec22a351a877ef0b987b372f68 | |
parent | f8d516e5004cfcf3460b91018396c6abcd5a765e [diff] |
Reclassify RemoteActionFileSystem as an in-memory filesystem, and rename the ActionFileSystemType enum values to better match reality. RemoteActionFileSystem, the action filesystem implementation used by Bazel, became an in-memory filesystem in revision 2876569. Its ActionFileSystemType must be recognized as such so that Skyframe creates output directories prior to local action execution. The correspondence between old -> new enum values is as follows: DISABLED -> DISABLED STAGE_REMOTE_FILES -> REMOTE_FILE_SYSTEM IN_MEMORY_FILE_SYSTEM -> IN_MEMORY_ONLY_FILE_SYSTEM IN_MEMORY_FILE_SYSTEM_AND_STAGE_REMOTE_FILES -> STAGE_REMOTE_FILES_FILE_SYSTEM Also fix a call site where a capability check was made by comparing with the enum value instead of calling the accessor. PiperOrigin-RevId: 482270459 Change-Id: I8ba6a0f32d8570e81281e1e1a29b232df2ac6c85
{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