gradle/actions
1
0
Fork 0
mirror of https://github.com/gradle/actions synced 2025-01-19 05:42:35 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Add link to GitHub docs
Some checks are pending
CI-check-and-unit-test / check-format-and-unit-test (push) Waiting to run
Details
CI-codeql / Analyze (push) Waiting to run
Details
CI-init-script-check / test-init-scripts (push) Waiting to run
Details
CI-integ-test / build-distribution (push) Waiting to run
Details
CI-integ-test / caching-integ-tests (push) Blocked by required conditions
Details
CI-integ-test / other-integ-tests (push) Blocked by required conditions
Details
CI-ossf-scorecard / Scorecard analysis (push) Waiting to run
Details
CI-update-dist / update-dist (push) Waiting to run
Details
CI-validate-wrappers / validation (push) Waiting to run
Details

Browse source
This commit is contained in:
Daz DeBoer 2024-12-10 10:50:29 -07:00 committed by GitHub
parent 00781cbaae
commit 375738a38b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/setup-gradle.md
View file

@ -127,6 +127,8 @@ cache-disabled: true
By default, The `setup-gradle` action will only write to the cache from Jobs on the default (`main`/`master`) branch.
Jobs on other branches will read entries from the cache but will not write updated entries.
This setup is designed around [GitHub imposed restrictions on cache access](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache) and should work well in most scenarios.
See [Optimizing cache effectiveness](#select-which-branches-should-write-to-the-cache) for a more detailed explanation.
In some circumstances, it makes sense to change this default and configure a workflow Job to read existing cache entries but not to write changes back.