Github Cache Eviction Policy #3226
Closed
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
WeiqunZhang
force-pushed
the
gh_cache_eviction
branch
from
ddf2d8e
to
4223b1d
Compare
WeiqunZhang
force-pushed
the
gh_cache_eviction
branch
4 times, most recently
from
92b1490
to
e68f468
Compare
After a workflow finishes, delete all old caches associated with it. Add an action to delete caches associated with a PR upon the close of the PR. Use variables in github context as part of the cache key names instead of manually repeating.
WeiqunZhang
force-pushed
the
gh_cache_eviction
branch
from
e68f468
to
ed80445
Compare
|
This won't work because of the lack of write permission. |
|
Argh |
|
This is now implemented in #3229 with a different approach. |
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.
After a workflow finishes, delete all old caches associated with it.
Add an action to delete caches associated with a PR upon the close of the PR.
Use variables in the github context as part of the cache key names instead of manually repeating.
This is how cache works now. There is a cache file for the default branch (i.e., development). When
a PR is submitted, the main cache file is checked out to be used by the PR. When the PR finishes
the CIs, a copy of the cache including any updates will be saved. This cache has a scope associated
with the PR. Another PR will be be able to access it. If the author pushes an update to the BR branch,
The new CIs will run using the latest PR cache and it will evict old cache in the PR. When the PR is
merged, its cache will be deleted. The development branch's workflow will generate the latest main
cache.