Repository navigation
Add cache-provider: external to skip Gradle User Home caching - #1059
Merged
Merged
Conversation
Users relying on an external mechanism to save/restore Gradle User Home (e.g. Develocity Artifact Cache) previously had to set cache-disabled: true, which is confusing since caching isn't actually disabled — it's just not managed by this action — and the Job Summary misleadingly reported caching as "Disabled". cache-provider: external skips Gradle User Home restore/save (same as cache-disabled) but reports a distinct "External" status in the Job Summary, explaining that caching is handled by another provider. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Gradle Builds captured by gradle/actions/setup-gradleDemo adding Build Scan® comment to PR :: successful-build-with-always-comment
|
- integ-test-caching-config: mirrors the pre-existing-Gradle-User-Home test, but with cache-provider: external, proving that a pre-existing Gradle User Home doesn't trigger the usual skip-with-warning behavior and that Build Scans are still captured. - demo-job-summary: adds a job so the "External" caching Job Summary variant has a live example alongside the other cache-provider demos. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Mirror caching-config-cache-disabled instead of the pre-existing-GUH variant: test that Build Scans are captured with cache-provider: external, without conflating it with the pre-existing Gradle User Home scenario. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
No need to matrix across OSes for this test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The previous commit was formatted by a stale local prettier (3.8.4) rather than the pinned 3.9.6, so CI's prettier-check rejected it: 3.9.6 collapses these unions onto one line, since they fit within printWidth 120. Add a trailing comment to each member, which both documents the statuses and keeps the multi-line layout that prettier preserves — matching the existing ProjectCacheStatus style in this file. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users relying on an external mechanism to save/restore Gradle User Home (e.g. Develocity Artifact Cache) previously had to set cache-disabled: true, which is confusing since caching isn't actually disabled — it's just not managed by this action — and the Job Summary misleadingly reported caching as "Disabled".
cache-provider: external skips Gradle User Home restore/save (same as cache-disabled) but reports a distinct "External" status in the Job Summary, explaining that caching is handled by another provider.