mirror of
https://github.com/gradle/actions.git
synced 2026-08-17 11:22:50 +00:00
Daz DeBoerandClaude Opus 5
528e626588
Partial revert of the extraction in #1027. The caching smoke test should answer one question quickly: does a seeded cache let a later build run --offline? Everything else is integration-level. smoke-test-restore-gradle-home now has just two jobs: seed the cache, then verify --offline. The build-cache, no-extracted-cache-entries-restored and pre-existing-gradle-home jobs move to a restored integ-test-restore-gradle-home, wired back into suite-integ-test-caching. The seed-build job is intentionally duplicated across the two workflows. They use distinct cache keys, since both suites run concurrently and would otherwise write to the same entry. pre-existing-gradle-home stays pinned to ubuntu-latest, keeping the reason recorded: pre-creating ~/.gradle is what stops setup-gradle relocating the Gradle User Home to D:\a\.gradle on Windows, so the job looks for a cache entry rooted at a different path than the seed build saved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>