Configurable save cache on failure
See original GitHub issueCurrently this cache action will only save caches if all tests succeed. In many cases this is desirable behavior. However I have some projects with long build times and flakey test suites. It would be very helpful if I could configure the cache to be saved regardless of the test suite success or failure.
I have created a fork of this project action to set the post-if to always()
.
Is it possible to make the cache policy configurable? Or to pass post-if as an argument from the cache configuration?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:163
- Comments:40 (6 by maintainers)
Top Results From Across the Web
Setting for GitLab CI to cache on failure (#56458) · Issues
Having the cache available on failure would allow to pass that file in the same pipeline. We configured the job like this :....
Read more >Configuration cache - Gradle User Manual
The configuration cache is a feature that significantly improves build performance by caching the result of the configuration phase and reusing this for ......
Read more >configuration-cache enabled causes build to fail
org.gradle.unsafe.configuration-cache=true. And this is the error that i'm receiving. FAILURE: Build failed with an exception.
Read more >How caching fails - Section.io
A highly effective website cache is optimised to store and share every possible response that only contains information relevant to all users, ...
Read more >Configure the client cache - Configuration Manager
If content is in the cache and it's the correct version, the client uses the cached content. When the required version of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems like it would make a lot of sense in some circumstances.
Say I have following steps:
It would make sense if post cache could happen conditionally on success of dependencies install, code style step is irrelevant to it.
Next fork with latest upstream changes (including the new 5GB cache limit): https://github.com/marketplace/actions/always-upload-cache