cowwoc commented on PR #392: URL: https://github.com/apache/maven-build-cache-extension/pull/392#issuecomment-3372275419
> I wonder why the permissions on machine X should be the same as those on the build from machine Y. This could lead to problems with cache portability since file metadata is not included in the file checksum - only the content of the file is. The cache doesn't track the permissions in checksums, and changing permissions doesn't affect caching. While I understand the relevance of timestamps, the significance of permissions is less clear to me. Perhaps permissions should only be synced when the build explicitly sets them on outputs, otherwise it becomes a replication of environment which is a slightly different concern. 1. I know that you designed this extension for CIs but it sounds like most of the users reporting problems are actually using it for local development. 2. https://github.com/apache/maven-build-cache-extension/issues/214 discusses one scenario where the current behavior causes problems 3. In the context of preserving permissions across machines, perhaps we should model this after git? It preserves permissions across multiple machines. Are you okay with its approach? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
