MINOR Bump setup-gradle version

[mumrah]

No description provided.

[mumrah]

I noticed our GHA cache is empty. I'd like to see if just upgrading the setup-gradle plugin is enough to fix it.

[chia7712]

I noticed our GHA cache is empty.

Pardon me, the following message originates from this PR. Is this behavior expected? It appears that the cache key remains unchanged despite the bump in setup-gradle.

Restore Gradle state from cache
  Requesting Gradle User Home with
      key:gradle-home-v1|Linux-X64|validate[b8a35c2f917259958c9abe8f2ff1b5ff]-a4f1b015bf12a5848020f23c9b19dfed36c418f0
      restoreKeys:[gradle-home-v1|Linux-X64|validate[b8a35c2f917259958c9abe8f2ff1b5ff],gradle-home-v1|Linux-X64|validate,gradle-home-v1|Linux-X64]
  Using cache paths: /home/runner/.gradle/caches,/home/runner/.gradle/notifications,/home/runner/.gradle/jdks,/home/runner/.gradle/.setup-gradle
  Warning: Cache not found for keys: gradle-home-v1|Linux-X64|validate[b8a35c2f917259958c9abe8f2ff1b5ff]-a4f1b015bf12a5848020f23c9b19dfed36c418f0, gradle-home-v1|Linux-X64|validate[b8a35c2f917259958c9abe8f2ff1b5ff], gradle-home-v1|Linux-X64|validate, gradle-home-v1|Linux-X64
  Gradle User Home cache not found. Will initialize empty.

[mumrah]

@chia7712 I don't think a change to the setup-gradle action version will affect the cache keys. Details on how the cache keys are computed can be found here https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#cache-keys

Also, we wouldn't expect to see a PR writing to the cache since we set gradle-cache-read-only: true in the action (only trunk builds write to the cache)

[chia7712]

@mumrah thanks for your explanation. My main question is: "Why doesn't this PR utilize the cache, despite the cache keys remaining unchanged?" - The other PR having the same cache keys can use the cache to restore the gradle stuff

[mumrah]

Thanks for the clarification @chia7712. This PR isn't utilizing the cache, because the cache is empty https://github.com/apache/kafka/actions/caches 🥲. I am hoping that bumping the setup-gradle version will fix things

[chia7712]

LGTM

This PR isn't utilizing the cache, because the cache is empty https://github.com/apache/kafka/actions/caches

That's odd, as the last build of trunk successfully update the Gradle cache.

  Caching Gradle User Home with cache key: gradle-home-v1|Linux-X64|test[188616818c9a3165053ef8704c27b28e]-c2b38503f2901ff3b1e92b99a8527fdc62acb77e
  Using cache paths: /home/runner/.gradle/caches,/home/runner/.gradle/notifications,/home/runner/.gradle/jdks,/home/runner/.gradle/.setup-gradle
  /usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /home/runner/work/kafka/kafka --files-from manifest.txt --use-compress-program zstdmt
  Cache Size: ~257 MB (269612194 B)
  Cache saved successfully

I am hoping that bumping the setup-gradle version will fix things

+1000