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

Cache Failing. Switch to Self-Hosted Cache #534

Open
timothystewart6 opened this issue Jun 19, 2024 · 0 comments
Open

Cache Failing. Switch to Self-Hosted Cache #534

timothystewart6 opened this issue Jun 19, 2024 · 0 comments
Labels
CI Related to continuous integration and testing

Comments

@timothystewart6
Copy link
Contributor

timothystewart6 commented Jun 19, 2024

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

image

@timothystewart6 timothystewart6 added the CI Related to continuous integration and testing label Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Related to continuous integration and testing
Projects
None yet
Development

No branches or pull requests

1 participant