The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/ci/gradle-cache-writer-by-major has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: ce6f680bcef7703744308ea2d35fd324bb1c0ea2 / James Daugherty <[email protected]> Decide Gradle cache writes in one shared action, and document the policy The cache decision was a bash step in the core build and a literal cache-read-only: true on every other setup-gradle step, so changing the policy meant editing every workflow on every branch. It now lives in the local action .github/actions/gradle-cache-policy, which every setup-gradle step runs first and takes cache-read-only from. Only the core build passes cache-writer, from its matrix entry flagged for each OS; release verification stays uncached and does not use it. AGENTS.md gains a critical rule and a "Gradle caching" section that record the rules and why: GitHub's 10 GB per-repository cache, the branch scoping that lets a run read only its own branch and the default branch, the job-id prefix fallback that made the core build restore the Forge build's cache, and the size of a writer's entries. Report URL: https://github.com/apache/grails-core/actions/runs/38629653136 With regards, GitHub Actions via GitBox
