Reviewing files that changed from the base of the PR and between 185a4a5 and caf810d.

• gradle.properties (1 hunks)

gradle.properties (1)

48-48:

❌ Incorrect review comment

Ensure compatibility with supported Gradle versions.

The org.gradle.configuration-cache.entries-per-key property was introduced in recent Gradle releases. Please confirm that your Gradle wrapper (gradle/wrapper/gradle-wrapper.properties) points to a version that supports this setting, and bump it if necessary to prevent unknown-property errors or warnings.

---

🏁 Script executed:

#!/bin/bash
# Extract the Gradle wrapper distribution version
grep '^distributionUrl' gradle/wrapper/gradle-wrapper.properties | sed -E 's|.*/gradle-(.*)-all\.zip|\1|'

Length of output: 186

---

🌐 Web query:

site:docs.gradle.org "entries-per-key"

💡 Result:

Here are relevant details from the Gradle documentation regarding the "entries-per-key" property:

---

entries-per-key in Gradle

The phrase "entries-per-key" typically appears in the context of Gradle's Build Cache or Configuration Cache, particularly with the file-system build cache backend.

File System Build Cache Settings

Within the configuration options for the file system build cache, you can find the setting:

entries-per-key

• Property: entries-per-key
• Scope: build cache (file system backend)
• Type: Integer
• Description:
  Specifies the maximum number of cache entries per cache key that will be stored in the directory. If more entries are created for a key, the oldest entries are deleted. This helps limit the size and disk usage of the local build cache.
• Default value:
  1 (Only the most recent entry per key is kept)

Example Configuration in settings.gradle:

buildCache {
    local {
        directory = "${rootDir}/.gradle/build-cache"
        removeUnusedEntriesAfterDays = 30
        entriesPerKey = 2 // Keep up to two entries per key
    }
}

Documentation Reference

For more details, see:

• Gradle User Manual – Build Cache Configuration
• FileSystemBuildCache Documentation

---

In summary:
The entries-per-key property is used to control how many build cache entries are stored per key when using the file system build cache backend in Gradle. It helps manage cache size and ensures old cache data is cleaned up efficiently.

---

🌐 Web query:

site:docs.gradle.org "org.gradle.configuration-cache.entries-per-key"

💡 Result:

Based on the provided search results from docs.gradle.org, the property org.gradle.configuration-cache.entries-per-key is not mentioned in the available documentation. However, here's a summary of relevant configuration cache settings from the Gradle User Manual:

---

Configuration Cache Settings

• org.gradle.configuration-cache:
  Enables/disables the feature entirely (true/false)¹.
• Key Configuration Inputs:
  Build scripts, environment variables, system properties, files read during configuration, and JVM parameters².
• Serialization:
  Uses optimized serialization for task graphs and avoids Java serialization for performance².
• Parallelization:
  Parallel task execution and cache entry loading (enabled by default from Gradle 8.11)³.

For advanced cache tuning, Gradle's documentation²¹ does not currently describe a property for limiting cache entries per key. Such a setting might relate to internal implementation details or future updates not covered here. Check the latest Gradle release notes or issue tracker for additions beyond the provided documents.

Citations:

• 1: https://docs.gradle.org/current/userguide/configuration_cache.html
• 2: https://docs.gradle.org/current/userguide/build_cache.html
• 3: https://blog.gradle.org/road-to-configuration-cache
• 4: https://docs.gradle.com/build-cache-node
• 5: https://blog.gradle.org/introducing-configuration-caching
• 6: https://docs.gradle.org/current/userguide/build_environment.html
• 7: https://github.com/gradle/actions/blob/main/docs/setup-gradle.md
• 8: https://github.com/gradle/configuration-cache-report
• 9: https://developer.squareup.com/blog/5-400-hours-a-year-saving-developers-time-and-sanity-with-gradles/
• 10: https://cookbook.gradle.org/plugin-development/configuration-cache/

---

Remove invalid Gradle property

The org.gradle.configuration-cache.entries-per-key setting is not recognized in any current Gradle release (it’s not documented in Gradle’s Configuration Cache or Build Cache guides). It appears to be an invalid property. If your goal is to cap build‐cache entries per key, use the Gradle DSL in settings.gradle:

buildCache {
  local {
    entriesPerKey = 2
    // …
  }
}

Please remove or correct this line in gradle.properties:

• gradle.properties:
  org.gradle.configuration-cache.entries-per-key=100

Likely an incorrect or invalid review comment.