examples: Reuse cargo registry cache across OSes

The registry filesystem format and the git repositories work
across platforms, no need to maintain runner-specific
caches for these.
This commit is contained in:
Mikhail Zabaluev 2020-05-21 13:10:26 +03:00
parent 984ce638f0
commit 5e5fbe724b

View file

@ -251,7 +251,7 @@ Esy allows you to export built dependencies and import pre-built dependencies.
...(Build job)... ...(Build job)...
# Re-export dependencies if anything has changed or if it is the first time # Re-export dependencies if anything has changed or if it is the first time
- name: Setting dependency cache - name: Setting dependency cache
run: | run: |
esy export-dependencies esy export-dependencies
if: steps.restore-cache.outputs.cache-hit != 'true' if: steps.restore-cache.outputs.cache-hit != 'true'
@ -428,13 +428,18 @@ When dependencies are installed later in the workflow, we must specify the same
## Rust - Cargo ## Rust - Cargo
```yaml ```yaml
- uses: actions/cache@v2 - name: Cache cargo dependencies
uses: actions/cache@v2
with: with:
path: | path: |
~/.cargo/registry ~/.cargo/registry
~/.cargo/git ~/.cargo/git
target key: cargo-deps-${{ hashFiles('**/Cargo.lock') }}
key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }} - name: Cache cargo build
uses: actions/cache@v2
with:
path: target
key: ${{ runner.os }}-cargo-build-${{ hashFiles('**/Cargo.lock') }}
``` ```
## Scala - SBT ## Scala - SBT