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

Proper caching solution for self hosted runners #66

Closed
AmyrAhmady opened this issue Dec 14, 2022 · 2 comments
Closed

Proper caching solution for self hosted runners #66

AmyrAhmady opened this issue Dec 14, 2022 · 2 comments

Comments

@AmyrAhmady
Copy link

AmyrAhmady commented Dec 14, 2022

Hey there,
Thank you for your work on this action, we really appreciate this
I came here to ask if it's possible to have a "locally" cached solution for CMake (and maybe Ninja) using this Node package:
https://github.com/actions/toolkit/tree/master/packages/tool-cache
(Note: I know you are already using it for downloading and extracting archives, but it's not creating locally cached binaries in _tool directory)

It is also used in this https://github.com/actions/setup-python and it speeds things a lot to use already stored local binaries instead of pulling them on each run

Just a screenshot of where cached files go:
image

@lukka
Copy link
Owner

lukka commented Dec 14, 2022

@AmyrAhmady i think I had the usage of the tool-cache long ago but I dropped since I felt nobody used it.
For self hosted runners it makes it very important indeed.

lukka added a commit that referenced this issue Dec 17, 2022
lukka added a commit that referenced this issue Dec 18, 2022
@lukka
Copy link
Owner

lukka commented Dec 18, 2022

@AmyrAhmady solved in release https://github.com/lukka/get-cmake/releases/tag/local-cache
Let me know if it looks good!

@lukka lukka closed this as completed Dec 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants