mirror of
https://github.com/gradle/actions.git
synced 2026-08-17 11:22:50 +00:00
ca8d95717f
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. Replaces #1031 and #1030, squashed into a single commit. ## Layout `smoke-test-restore-gradle-home.yml` — two jobs: | job | purpose | |---|---| | `restore-gradle-home-seed-build` | seed the cache | | `restore-gradle-home-dependencies-cache` | verify the restored cache allows `--offline` | `integ-test-restore-gradle-home.yml` — restored, wired back into `suite-integ-test-caching`: | job | purpose | |---|---| | `restore-gradle-home-seed-build` | seed the cache (duplicated, see below) | | `restore-gradle-home-build-cache` | local build-cache restored | | `restore-gradle-home-no-extracted-cache-entries-restored` | build works with cache entries skipped | | `restore-gradle-home-pre-existing-gradle-home` | pre-existing GUH overwritten by restore | This file is identical to the pre-#1027 original except for the `dependencies-cache` job, which the smoke test now owns. All four jobs keep the `runner-os` matrix. ## Notes **The seed job is duplicated, with distinct cache keys.** The smoke suite uses `smoke-test-restore-gradle-home-*`; the integ suite keeps `restore-gradle-home-*`. This matters: `smoke-tests` and `caching-integ-tests` run concurrently in `ci-integ-test.yml`, so sharing a key would have both suites racing to write the same entry. **Distinct workflow `name:`.** The smoke workflow is `Smoke test restore Gradle Home`, so the two don't appear identically in the Actions UI. **One thing to be aware of for the future:** `restore-gradle-home-pre-existing-gradle-home` cannot pass on Windows. Pre-creating `~/.gradle` is what stops `setup-gradle` relocating the Gradle User Home to `D:\a\.gradle`, so the job looks for a cache entry rooted at a different path than the seed build saved and never matches it. The caching integ suite runs ubuntu-only, so this is not a problem today — but adding Windows to that suite would surface it. ## Verification All workflow YAML parses, and every local `uses:` reference resolves — no dangling paths after the rename and re-add. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
60 lines
1.5 KiB
YAML
60 lines
1.5 KiB
YAML
name: suite-integ-test-caching
|
|
|
|
on:
|
|
workflow_call:
|
|
inputs:
|
|
runner-os:
|
|
type: string
|
|
default: '["ubuntu-latest"]'
|
|
skip-dist:
|
|
type: boolean
|
|
default: false
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
cache-cleanup:
|
|
uses: ./.github/workflows/integ-test-cache-cleanup.yml
|
|
with:
|
|
runner-os: '${{ inputs.runner-os }}'
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
caching-config:
|
|
uses: ./.github/workflows/integ-test-caching-config.yml
|
|
with:
|
|
runner-os: '${{ inputs.runner-os }}'
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
restore-containerized-gradle-home:
|
|
uses: ./.github/workflows/integ-test-restore-containerized-gradle-home.yml
|
|
with:
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
restore-custom-gradle-home:
|
|
uses: ./.github/workflows/integ-test-restore-custom-gradle-home.yml
|
|
with:
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
restore-gradle-home:
|
|
uses: ./.github/workflows/integ-test-restore-gradle-home.yml
|
|
with:
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
restore-java-toolchain:
|
|
uses: ./.github/workflows/integ-test-restore-java-toolchain.yml
|
|
with:
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
sample-kotlin-dsl:
|
|
uses: ./.github/workflows/integ-test-sample-kotlin-dsl.yml
|
|
with:
|
|
runner-os: '${{ inputs.runner-os }}'
|
|
skip-dist: ${{ inputs.skip-dist }}
|
|
|
|
sample-gradle-plugin:
|
|
uses: ./.github/workflows/integ-test-sample-gradle-plugin.yml
|
|
with:
|
|
runner-os: '${{ inputs.runner-os }}'
|
|
skip-dist: ${{ inputs.skip-dist }}
|