Daz DeBoer 76ea8a76b2 Treat configuration-cache as an extracted entry ... Instead of using a fallback strategy to locate a configuration-cache entry based on the current job and git SHA, these entries are now keyed based on their file content with the keys persisted in the primary Gradle User Home entry. This removes the chance of having a configuration-cache entry restored that is incompatible with the restored Gradle User Home state, and makes the logic easier to understand. This change involved a fairly major refactor, with the CacheEntryExtractor being split out from the primary cache implementation, and adding a separate extractor implementation for configuration-cache.		2021-12-30 16:03:02 -07:00
..
cache-base.ts	Treat configuration-cache as an extracted entry	2021-12-30 16:03:02 -07:00
cache-extract-entries.ts	Treat configuration-cache as an extracted entry	2021-12-30 16:03:02 -07:00
cache-reporting.ts	Extract cache-reporting into separate file	2021-12-08 15:09:26 -07:00
cache-utils.ts	Treat configuration-cache as an extracted entry	2021-12-30 16:03:02 -07:00
caches.ts	Treat configuration-cache as an extracted entry	2021-12-30 16:03:02 -07:00
execution.ts	Allow action to be used without Gradle invocation	2021-12-17 10:29:58 -07:00
gradlew.ts	Allow source files to contain lines up to 120 characters	2021-10-29 07:50:06 -06:00
main.ts	Allow action to be used without Gradle invocation	2021-12-17 10:29:58 -07:00
post.ts	Refactor: use a single .json file to describe all cached artifact bundles (#121)	2021-11-28 10:19:56 -07:00
provision.ts	Avoid failing build on distributions cache errors	2021-11-05 07:01:48 -06:00