The GitHub Actions job "CI" on grails-core.git/ci/gradle-cache-single-writer has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 33de4d48f0e44072c0fcd8b45f6272ccf5ccbb50 / James Daugherty <[email protected]> Write the Gradle User Home cache from one core build job per OS Every caching setup-gradle step wrote an entry on each branch push, about 25 per push and 3.5 GiB on 8.x, so the repository sat above GitHub's 10 GB cache limit and evicted entries within hours. Entries for Windows, macOS and the less active release branches never survived, those jobs started with an empty Gradle User Home, and a single failed download from Maven Central or the plugin portal failed the job. A job whose own entry had been evicted also fell back to whichever entry shared its job id as a prefix, so the core build restored the Forge build's cache. Only the core build job now writes, from the matrix entries flagged cache_writer: Ubuntu on the branch's baseline JDK and Windows. Every other caching step is read-only and restores the newest entry for its OS, which setup-gradle falls back to after the job's own keys, and downloads whatever that entry lacks. This is the arrangement setup-gradle's documentation recommends for keeping cache use within the limit. A release run, which writes only tag-scoped entries, is read-only too. Report URL: https://github.com/apache/grails-core/actions/runs/38615214991 With regards, GitHub Actions via GitBox
