-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Enable ccache in CI #290
Enable ccache in CI #290
Conversation
This reverts commit 335d72f.
We are caching a particular version of each apt dependency. Does the "included action" update the cache with the new versions when they are available? My hunch is that it will be rare for an apt dependency to break building Jank. But we might want to periodically evict the cache to get new versions. This will keep us informed if a new version of a dependency breaks Jank. |
You're correct. Github has its own cache eviction mechanism, but we may still end up in a situation where an upstream dependency will break jank but CI doesn't get it. I'm open to solutions for that, going forward, but not trying to solve everything here. |
f834631
to
2875baf
Compare
BppTree has a ton of them and I think they're just for testing and benchmarking.
This should drastically cut our CI job times, hopefully allowing us to run CI on PR creation and synchronization, as we were before.