snazy commented on PR #3381: URL: https://github.com/apache/polaris/pull/3381#issuecomment-3723319561
For posterity, Gradle's `setup-gradle` action provides functionality to cache Gradle distributions, see the [cache artifacts](https://github.com/apache/polaris/actions/caches) named `gradle-home-*`). The full name of such Gradle home cache artifacts also contains the strings `java-21` and `polaris-gradle[gradle]`. Those two pieces are configured via the `ci-incr-build-cache-prepare` action in the apache/polaris repo, via the environment variables `GRADLE_BUILD_ACTION_CACHE_KEY_ENVIRONMENT`, `GRADLE_BUILD_ACTION_CACHE_KEY_JOB` and `GRADLE_BUILD_ACTION_CACHE_KEY_JOB_INSTANCE`. Without setting those env vars, the release jobs would _not_ be able to reuse a cached Gradle-Home, so setting those is needed. Note that the total size for GitHub cache artifacts is limited to 10GB (LRU eviction policy). The easiest option would be to just use `ci-incr-build-cache-prepare`. Another thing I'd recommend is to make the cache read-only for releases (the default when using `ci-incr-build-cache-prepare`), to ensure that there is no way to leak sensitive data into cache artifacts. -- 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]
