gradle/gradle-build-action
1
0
Fork 0
mirror of https://github.com/gradle/gradle-build-action.git synced 2025-05-01 20:38:34 +02:00
Code Issues Projects Releases Packages Wiki Activity

Add experimental support for 'strict-match' caching

Browse source 
By default, the action will attempt to restore a Gradle User Home
cache entry from a different set of matrix inputs (or a different Job entirely)
if an existing entry is not found for the current Job (including matrix inputs).

By specifying the experimental `gradle-home-cache-strict-match` parameter, a user
can avoid this fuzzy matching and ensure that a job execution starts with an
empty Gradle User Home if no entry from a prior execution is found.
This commit is contained in:
Daz DeBoer 2022-01-19 11:35:50 -07:00
parent a8da4e5ca3
commit a23ac1d61c
No known key found for this signature in database
GPG key ID: DD6B9F0B06683D5D
2 changed files with 11 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
action.yml
View file

@ -48,8 +48,12 @@ inputs:
# EXPERIMENTAL & INTERNAL ACTION INPUTS
# The following action properties allow fine-grained tweaking of the action caching behaviour.
# These properties are not designed for production use, and may change without notice in a subsequent release of `gradle-build-action`.
# These properties are experimental and not (yet) designed for production use, and may change without notice in a subsequent release of `gradle-build-action`.
# Use at your own risk!
gradle-home-cache-strict-match:
description: When 'true', the action will not attempt to restore the Gradle User Home entries from other Jobs.
required: false
default: false
workflow-job-context:
description: Used to uniquely identify the current job invocation. Defaults to the matrix values for this job; this should not be overridden by users (INTERNAL).
required: false