Caching ValKey for self-hosted runners. #2544
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.
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.
The text was updated successfully, but these errors were encountered: