Daz DeBoer

This would address #115

Thanks for the report. Any chance you could contribute a PR for the fix? I don't have any access to self-hosted runners to test things on. It looks like you'd...

Thanks for you report. Indeed it could make sense to be able to save/restore the configuration-cache state even with a persistent Gradle User Home. There are a couple of things...

> I had assumed that the provisioned version would be available in Gradle user home's wrappers, but that doesn't seem to be the case, so that would mean downloading the...

Experimental support for Gradle User Home cleanup has been released in `v2.3.0-beta.1`. Please try this version (with cache-cleanup enabled) and let us know how it works for you. ``` -...

Hmmm. This is a good point: the cache key will never change for this entry, so you'll never recover from this situation. Options you currently have are: - Disable the...

I've raised #116 as the quick solution to avoid failing the build in this case.

So I've pushed a fix for #116, but looking at your failure more closely I can see this won't help in your case. This is because the cache entry was...

> @bigdaz so we're still missing a retry logic or something similar to deal with corrupt cache entries as mentioned above? Not exactly. If the cache entry is fine, but...

Currently, the only option you have from `gradle-build-action` is to specify a new "Cache Key Prefix" for the workflow, which will have the same effect as purging the entire cache....