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

Caching ValKey for self-hosted runners. #2544

Open
avifenesh opened this issue Oct 30, 2024 · 0 comments
Open

Caching ValKey for self-hosted runners. #2544

avifenesh opened this issue Oct 30, 2024 · 0 comments
Labels
CI/CD CI/CD related OPS Operation matters, which are not CI/CD optimization Optimization which are not performance or a feature per-se.

Comments

@avifenesh
Copy link
Collaborator

Self-hosted runners are actually cloning the repo and since it's an actual machine that stay caching won't work, the state of the bin is dependent on the last run and not on the repo.
Therefore, using the cache from the previous run will not work as expected, there's an extra logic to create caching, it might be having few bins, and replacing the symlink for each round or something similar. The current state will check the state of the version and will clone and build based on needs.
We need to find a way to cache the ValKey repo on the runner itself.

@avifenesh avifenesh added optimization Optimization which are not performance or a feature per-se. CI/CD CI/CD related OPS Operation matters, which are not CI/CD labels Oct 30, 2024
@Yury-Fridlyand Yury-Fridlyand mentioned this issue Nov 5, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD CI/CD related OPS Operation matters, which are not CI/CD optimization Optimization which are not performance or a feature per-se.
Projects
Status: No status
Development

No branches or pull requests

1 participant