BUILD-8977 custom Gradle cache

[mikolaj-matuszny-ext-sonarsource]

BUILD-8977

• disabled caching mechanism built in setup-gradle - this is required but also has a slight downside of false information in job summary. With moving towards having dedicated setup-gradle action this should be resolved soon.

1. Cache Key Generation

   • Based on SonarSource standard pattern used across Cirrus CI configurations:

     find -type f \( -name "*.gradle*" -or -name "gradle*.properties" \) | sort | xargs cat

   • GitHub Actions adaptation: Generates MD5 hash from all Gradle configuration files:
     • All *.gradle and *.gradle.kts files (matches *.gradle* pattern)
     • gradle/libs.versions.toml (version catalog)
     • gradle/wrapper/gradle-wrapper.properties (matches gradle*.properties pattern)
   • Key difference from Cirrus CI: Excludes gradle.properties (modified during build with unique version numbers)
   • Creates composite cache key: gradle-${{ runner.os }}-${{ github.workflow }}-${{ hash }}

2. Cached Directories

   • ${{ env.GRADLE_USER_HOME }}/caches - Gradle build cache and dependencies
   • ${{ env.GRADLE_USER_HOME }}/wrapper - Gradle wrapper distributions
   • Custom paths via cache-paths input (optional)

3. Cache Restore Strategy

   • Primary key: Full hash-based key for exact matches
   • Fallback keys: gradle-${{ runner.os }}-${{ github.workflow }}- for partial matches

This is based on CirrusCI usage as well as usage in teams that migrated to GitHub already.

[julien-carsique-sonarsource]

Please specify in the Jira ticket and describe in the PR, the chosen implementation.
Did you find the previous custom usages in Cirrus CI?
There is need for

• customization parameters in addition to the default values
  • custom path
  • custom key (based on custom script)
  • runner.os in the key?
  • github.workflow in the key (as in build-maven)

[sonarqubecloud]

🤖 Pull Request summary

This PR implements custom Gradle caching to replace the default setup-gradle caching mechanism.

• Adds two new inputs: cache-paths for additional cache directories and disable-caching toggle
• Disables built-in Gradle caching by setting cache-disabled: true in setup-gradle action
• Implements custom cache key generation using MD5 hashes of all Gradle build files
• Adds manual cache restoration step using SonarSource cache action with generated keys

Review focus: Verify the cache key generation logic covers all relevant Gradle files and that the fallback restore-keys pattern provides adequate cache hit rates.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud