Commit 0f87c3a
committed
fix: use setup-gradle for Gradle caching in CI
The run-tests job runs inside a ubuntu:24.04 container, so the home-relative Gradle cache paths resolve to a container-local home that does not exist when actions/cache validates them. This produces a Path Validation Error warning every run and the cache is never persisted.
Replace the two manual actions/cache steps with gradle/actions/setup-gradle, which resolves GRADLE_USER_HOME correctly on host and container runners, uses Gradle-aware cache keys, and is the upstream-recommended caching approach.
Pinned to the same SHA already used by gradle-wrapper-validation.yml.1 parent 469e167 commit 0f87c3a
1 file changed
Lines changed: 8 additions & 18 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
16 | | - | |
17 | | - | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
33 | | - | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
0 commit comments