You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
@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.
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:
The text was updated successfully, but these errors were encountered: