Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provide a save-cache-always setting #105

Open
tomsit-ionos opened this issue Nov 9, 2024 · 0 comments
Open

provide a save-cache-always setting #105

tomsit-ionos opened this issue Nov 9, 2024 · 0 comments

Comments

@tomsit-ionos
Copy link

tomsit-ionos commented Nov 9, 2024

Is your feature request related to a problem? Please describe.

When the WF fails, then the maven cache is being invalidated.
This is and needles and very bothersome due to cluttered logs when trying to fix an issue.

Describe the solution you'd like

I believe it is save to turn on the new cache 4.x feature by default -- or at least provide an option to set it.

I had seen this post https://stackoverflow.com/a/78376459/405749 this no-brainer ... until i learned that the setting got removed again. Hence i struck out my suggestion above.

However, there is this guide: https://github.com/actions/cache/blob/main/save/README.md#always-save-cache on how to do i for now.
My guess is, that it's not a no-brainer anymore but maybe there is a way.

Describe alternatives you've considered
I guess it's possible to configure an extra instance of the cache , but that is
a) discourages
b) redundant

Additional context

@tomsit-ionos tomsit-ionos changed the title cache should be saved always support a save cache always setting Nov 9, 2024
@tomsit-ionos tomsit-ionos changed the title support a save cache always setting privide a save-cache-always setting Nov 9, 2024
@tomsit-ionos tomsit-ionos changed the title privide a save-cache-always setting provide a save-cache-always setting Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant