You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks to the maintainers and contributors who keep this project up, which helps make CI cache handling simple! 馃コ
Use case
I have a build matrix with 5 jobs, that need to access (but not write) a common cache.
To update this cache, I have a job that this matrix depends on (that runs before it). This job restores cache and populates cache on a cache miss, so that subsequent jobs can use it.
This works, but there is an unneeded step of restoring cache in my first job, when all I want to do is to just test for a cache miss, rebuild in that case and upload new cache.
Proposal
There should be an input dry-run/test-cache/no-pull/[anything-else-here] (yes naming things is hard馃槄) that should control whether the cache is pulled initially (should default to yes). Then cache-hit should be set accordingly, and post cache step should run normally
First of all, thanks to the maintainers and contributors who keep this project up, which helps make CI cache handling simple! 馃コ
Use case
I have a build matrix with 5 jobs, that need to access (but not write) a common cache.
To update this cache, I have a job that this matrix depends on (that runs before it). This job restores cache and populates cache on a cache miss, so that subsequent jobs can use it.
This works, but there is an unneeded step of restoring cache in my first job, when all I want to do is to just test for a cache miss, rebuild in that case and upload new cache.
Proposal
There should be an input
dry-run/test-cache/no-pull/[anything-else-here](yes naming things is hard馃槄) that should control whether the cache is pulled initially (should default to yes). Thencache-hitshould be set accordingly, and post cache step should run normally