clayburn commented on PR #10448: URL: https://github.com/apache/nifi/pull/10448#issuecomment-3432567490
> Thanks for the updates @clayburn. > > Just for clarity on the implementation, setting `enabled` to `true` for the remote build cache means that it will always be used, but the `storeEnabled` expression means that results will only be sent in the context of authenticated GitHub Actions? You have the correct understanding—only authenticated GitHub Actions builds will write to the cache, which means only builds that originate from this repo. Builds originating from forks (i.e. PRs) will not be able to write to the cache. > Are there are any concerns around network accessibility, or server availability, of the remote build cache? It is a good consideration. If the server is unavailable, the builds will fallback to regular execution with the cache disabled. More specifically, the first remote cache error in any build will disable the remote cache for the remainder of the build. The one case which might matter in the context of OSS is the speed of the connection from local users to the remote cache. Users building locally on slow connections can potentially see the remote cache slowing down a build rather than speeding it up. In these cases we usually recommend the user disable remote caching themselves via [system property](https://docs.gradle.com/develocity/maven-extension/current/#disabling_the_remote_cache). -- 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]
