github: Fix database cache update #485
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: hamistao <[email protected]>
A github cache can not be updated using the same key, so instead we update using a different key each time but use the same key to restore it. Signed-off-by: hamistao <[email protected]>
hamistao
force-pushed
the
use-microcloud-cache-key
branch
from
425bda9
to
f5397ad
Compare
|
Can be rebased now. |
roosterfish
reviewed
Nov 14, 2024
| with: | ||
| path: /home/runner/vuln-cache | ||
| key: trivy-latest-cache | ||
| key: trivy-cache-${{ github.run_id }} |
There was a problem hiding this comment.
What is the default lifetime of those caches? Should we set it to e.g. one week so that GitHub can safely delete them afterwards?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A github cache can not be updated using the same key, so instead we update using a different key each time but use the same key to restore it.
Waiting until #474 is merged to rebase