-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add caching #428
Comments
aqua-installer doesn't support caching, but you can cache binaries using e.g. - uses: actions/cache@v3.3.1
with:
path: ~/.local/share/aquaproj-aqua
key: v1-aqua-installer-${{runner.os}}-${{runner.arch}}-${{hashFiles('aqua.yaml')}}
restore-keys: |
v1-aqua-installer-${{runner.os}}-${{runner.arch}}-
- uses: aquaproj/aqua-installer@v2.1.1
with:
aqua_version: v2.6.0 Please fix parameters properly. e.g. - uses: actions/cache@v3.3.1
with:
path: ~/.local/share/aquaproj-aqua
key: v1-aqua-installer-${{runner.os}}-${{runner.arch}}-${{hashFiles('.aqua/*.yaml')}} # Change key
restore-keys: |
v1-aqua-installer-${{runner.os}}-${{runner.arch}}- It's a bit difficult to run |
Note that by default aqua-installer runs aqua with -l option so packages that aren't run in the workflow aren't cached. - uses: aquaproj/aqua-installer@v2.1.1
with:
aqua_version: v2.6.0
aqua_opts: "" # Unset `-l` option But note that if So caching of aqua-installer is more complicated than you expect. |
Thanks @suzuki-shunsuke. Perhaps the action could just cache the aqua binary by default then? The parameters for that could be static. |
Rather than downloading all binaries on every run it would be more efficient and faster if the action would cache the aqua binary and all of the packages binaries.
https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows
https://github.com/actions/cache
The text was updated successfully, but these errors were encountered: