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
GitHub has no way to store cache outside of their servers, even for self-hosted runners. This means that sometimes our cache of vagrant boxes gets pushed out of cache before it can be used. Worse yet, there is a dangling cache right now that cannot be found yet it is using up our space. This will automatically purge after 24 hours but there's nothing we can do until then. I wish they support s3 compatible storage natively however they do not.
Because of these reasons, I am considering running a self-hosted cache server
GitHub has no way to store cache outside of their servers, even for self-hosted runners. This means that sometimes our cache of vagrant boxes gets pushed out of cache before it can be used. Worse yet, there is a dangling cache right now that cannot be found yet it is using up our space. This will automatically purge after 24 hours but there's nothing we can do until then. I wish they support s3 compatible storage natively however they do not.
Because of these reasons, I am considering running a self-hosted cache server
https://github.com/falcondev-oss/github-actions-cache-server
Otherwise I can attempt switch to an s3 compatible action here
https://github.com/tespkg/actions-cache
The text was updated successfully, but these errors were encountered: