gradle/actions
1
0
Fork 0
mirror of https://github.com/gradle/actions synced 2024-11-23 18:02:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Improve parameter description for 'cache-cleanup'
Some checks are pending
CI-check-and-unit-test / check-format-and-unit-test (push) Waiting to run
Details
CI-codeql / Analyze (javascript-typescript) (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-update-dist / update-dist (push) Waiting to run
Details

Browse source
This commit is contained in:
daz 2024-08-05 10:54:56 -06:00
parent 9edf610422
commit add58192d1
No known key found for this signature in database
2 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
dependency-submission/action.yml
View file

@ -60,7 +60,8 @@ inputs:
cache-cleanup:
description: |
Specifies if the action should attempt to remove any stale/unused entries from the Gradle User Home prior to saving to the GitHub Actions cache.
By default, no cleanup is performed. It can be configured to run every time, or only when all Gradle builds succeed for the Job.
By default ('on-success'), cleanup is performed when all Gradle builds succeed for the Job.
This behaviour can be disabled ('never'), or configured to always run irrespective of the build outcome ('always').
Valid values are 'never', 'on-success' and 'always'.
required: false
default: 'on-success'

3
setup-gradle/action.yml
View file

@ -43,7 +43,8 @@ inputs:
cache-cleanup:
description: |
Specifies if the action should attempt to remove any stale/unused entries from the Gradle User Home prior to saving to the GitHub Actions cache.
By default, no cleanup is performed. It can be configured to run every time, or only when all Gradle builds succeed for the Job.
By default ('on-success'), cleanup is performed when all Gradle builds succeed for the Job.
This behaviour can be disabled ('never'), or configured to always run irrespective of the build outcome ('always').
Valid values are 'never', 'on-success' and 'always'.
required: false
default: 'on-success'