2019-10-31 16:36:50 +01:00
# Examples
2020-02-26 23:43:11 +01:00
- [Examples ](#examples )
- [C# - NuGet ](#c---nuget )
2020-05-11 16:24:05 +02:00
- [D - DUB ](#d---dub )
2020-02-26 23:43:11 +01:00
- [Elixir - Mix ](#elixir---mix )
- [Go - Modules ](#go---modules )
- [Haskell - Cabal ](#haskell---cabal )
- [Java - Gradle ](#java---gradle )
- [Java - Maven ](#java---maven )
- [Node - npm ](#node---npm )
- [macOS and Ubuntu ](#macos-and-ubuntu )
- [Windows ](#windows )
- [Using multiple systems and `npm config` ](#using-multiple-systems-and-npm-config )
2020-03-20 21:02:11 +01:00
- [Node - Lerna ](#node---lerna )
2020-04-02 16:35:07 +02:00
- [Node - Yarn ](#node---yarn )
2020-02-26 23:43:11 +01:00
- [OCaml/Reason - esy ](#ocamlreason---esy )
- [PHP - Composer ](#php---composer )
- [Python - pip ](#python---pip )
- [Simple example ](#simple-example )
- [Multiple OS's in a workflow ](#multiple-oss-in-a-workflow )
2020-04-29 20:58:19 +02:00
- [Using pip to get cache location ](#using-pip-to-get-cache-location )
2020-02-26 23:43:11 +01:00
- [Using a script to get cache location ](#using-a-script-to-get-cache-location )
- [R - renv ](#r---renv )
- [Simple example ](#simple-example-1 )
- [Multiple OS's in a workflow ](#multiple-oss-in-a-workflow-1 )
- [Ruby - Bundler ](#ruby---bundler )
- [Rust - Cargo ](#rust---cargo )
- [Scala - SBT ](#scala---sbt )
- [Swift, Objective-C - Carthage ](#swift-objective-c---carthage )
- [Swift, Objective-C - CocoaPods ](#swift-objective-c---cocoapods )
- [Swift - Swift Package Manager ](#swift---swift-package-manager )
2019-10-31 16:36:50 +01:00
2019-12-10 01:21:47 +01:00
## C# - NuGet
2019-11-05 18:04:07 +01:00
Using [NuGet lock files ](https://docs.microsoft.com/nuget/consume-packages/package-references-in-project-files#locking-dependencies ):
2019-10-31 16:36:50 +01:00
2019-12-13 02:03:43 +01:00
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-12-13 02:03:43 +01:00
with:
path: ~/.nuget/packages
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
```
Depending on the environment, huge packages might be pre-installed in the global cache folder.
2020-05-26 20:58:07 +02:00
With `actions/cache@v2` you can now exclude unwanted packages with [exclude pattern ](https://github.com/actions/toolkit/tree/master/packages/glob#exclude-patterns )
```yaml
- uses: actions/cache@v2
with:
path: |
~/.nuget/packages
!~/.nuget/packages/unwanted
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
```
Or you could move the cache folder like below.
2019-12-16 01:45:29 +01:00
>Note: This workflow does not work for projects that require files to be placed in user profile package folder
2019-10-31 16:36:50 +01:00
```yaml
2019-12-10 01:21:47 +01:00
env:
NUGET_PACKAGES: ${{ github.workspace }}/.nuget/packages
steps:
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-12-10 01:21:47 +01:00
with:
path: ${{ github.workspace }}/.nuget/packages
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
2019-10-31 16:36:50 +01:00
```
2020-05-11 16:24:05 +02:00
## D - DUB
### POSIX
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-05-11 16:24:05 +02:00
with:
path: ~/.dub
key: ${{ runner.os }}-dub-${{ hashFiles('**/dub.json') }}
restore-keys: |
${{ runner.os }}-dub-
```
### Windows
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-05-11 16:24:05 +02:00
with:
path: ~\AppData\Local\dub
key: ${{ runner.os }}-dub-${{ hashFiles('**/dub.json') }}
restore-keys: |
${{ runner.os }}-dub-
```
2019-11-05 18:04:07 +01:00
## Elixir - Mix
2019-10-31 16:36:50 +01:00
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-10-31 16:36:50 +01:00
with:
2019-11-05 18:04:07 +01:00
path: deps
key: ${{ runner.os }}-mix-${{ hashFiles(format('{0}{1}', github.workspace, '/mix.lock')) }}
2019-10-31 16:36:50 +01:00
restore-keys: |
2019-11-05 18:04:07 +01:00
${{ runner.os }}-mix-
2019-10-31 16:36:50 +01:00
```
2019-11-05 18:04:07 +01:00
## Go - Modules
2019-11-05 17:03:56 +01:00
2019-10-31 16:36:50 +01:00
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-10-31 16:36:50 +01:00
with:
2019-11-05 18:04:07 +01:00
path: ~/go/pkg/mod
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
2019-10-31 16:36:50 +01:00
restore-keys: |
2019-11-05 18:04:07 +01:00
${{ runner.os }}-go-
2019-10-31 16:36:50 +01:00
```
2020-01-10 23:07:52 +01:00
## Haskell - Cabal
We cache the elements of the Cabal store separately, as the entirety of `~/.cabal` can grow very large for projects with many dependencies.
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
name: Cache ~/.cabal/packages, ~/.cabal/store and dist-newstyle
2020-01-10 23:07:52 +01:00
with:
2020-05-26 18:45:38 +02:00
path: |
~/.cabal/packages
~/.cabal/store
dist-newstyle
key: ${{ runner.os }}-${{ matrix.ghc }}
2020-01-10 23:07:52 +01:00
```
2019-10-31 16:36:50 +01:00
## Java - Gradle
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-10-31 16:36:50 +01:00
with:
path: ~/.gradle/caches
2020-03-18 14:40:55 +01:00
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*') }}
2019-10-31 16:36:50 +01:00
restore-keys: |
${{ runner.os }}-gradle-
```
## Java - Maven
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-10-31 16:36:50 +01:00
with:
path: ~/.m2/repository
key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
restore-keys: |
2019-10-31 20:08:09 +01:00
${{ runner.os }}-maven-
2019-10-31 16:36:50 +01:00
```
2019-11-05 18:04:07 +01:00
## Node - npm
2019-10-31 16:36:50 +01:00
2019-11-08 03:04:46 +01:00
For npm, cache files are stored in `~/.npm` on Posix, or `%AppData%/npm-cache` on Windows. See https://docs.npmjs.com/cli/cache#cache
2020-06-15 21:55:57 +02:00
If using `npm config` to retrieve the cache directory, ensure you run [actions/setup-node ](https://github.com/actions/setup-node ) first to ensure your `npm` version is correct.
2019-11-08 03:04:46 +01:00
>Note: It is not recommended to cache `node_modules` , as it can break across Node versions and won't work with `npm ci`
### macOS and Ubuntu
2019-10-31 16:36:50 +01:00
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-05 17:03:56 +01:00
with:
2019-11-08 03:04:46 +01:00
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
```
### Windows
```yaml
2020-03-19 03:05:56 +01:00
- name: Get npm cache directory
id: npm-cache
run: |
echo "::set-output name=dir::$(npm config get cache)"
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-08 03:04:46 +01:00
with:
2020-03-19 03:05:56 +01:00
path: ${{ steps.npm-cache.outputs.dir }}
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
2019-11-08 03:04:46 +01:00
restore-keys: |
${{ runner.os }}-node-
```
### Using multiple systems and `npm config`
2020-02-14 15:50:11 +01:00
```yaml
2019-11-08 03:04:46 +01:00
- name: Get npm cache directory
id: npm-cache
run: |
echo "::set-output name=dir::$(npm config get cache)"
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-08 03:04:46 +01:00
with:
path: ${{ steps.npm-cache.outputs.dir }}
2019-11-05 18:04:07 +01:00
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
2019-11-05 17:03:56 +01:00
restore-keys: |
2019-11-05 18:04:07 +01:00
${{ runner.os }}-node-
2019-10-31 16:36:50 +01:00
```
2020-04-02 16:35:07 +02:00
## Node - Lerna
```yaml
- name: restore lerna
2020-05-26 18:45:38 +02:00
uses: actions/cache@v2
2020-04-02 16:35:07 +02:00
with:
path: |
node_modules
*/* /node_modules
key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
```
2019-11-05 18:04:07 +01:00
## Node - Yarn
2019-11-13 16:18:47 +01:00
The yarn cache directory will depend on your operating system and version of `yarn` . See https://yarnpkg.com/lang/en/docs/cli/cache/ for more info.
2019-10-31 16:36:50 +01:00
```yaml
2020-02-14 15:50:11 +01:00
- name: Get yarn cache directory path
id: yarn-cache-dir-path
2019-11-13 16:18:47 +01:00
run: echo "::set-output name=dir::$(yarn cache dir)"
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-02-14 15:50:11 +01:00
id: yarn-cache # use this to check for `cache-hit` (`steps.yarn-cache.outputs.cache-hit != 'true'`)
2019-10-31 16:36:50 +01:00
with:
2020-02-14 15:50:11 +01:00
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
2019-11-13 16:18:47 +01:00
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
2019-10-31 16:36:50 +01:00
restore-keys: |
2019-11-05 18:04:07 +01:00
${{ runner.os }}-yarn-
2019-10-31 16:36:50 +01:00
```
2020-02-26 23:43:11 +01:00
## OCaml/Reason - esy
Esy allows you to export built dependencies and import pre-built dependencies.
```yaml
- name: Restore Cache
id: restore-cache
2020-05-26 18:45:38 +02:00
uses: actions/cache@v2
2020-02-26 23:43:11 +01:00
with:
path: _export
key: ${{ runner.os }}-esy-${{ hashFiles('esy.lock/index.json') }}
restore-keys: |
${{ runner.os }}-esy-
- name: Esy install
run: 'esy install'
- name: Import Cache
run: |
esy import-dependencies _export
rm -rf _export
...(Build job)...
# Re-export dependencies if anything has changed or if it is the first time
2020-05-21 12:10:26 +02:00
- name: Setting dependency cache
2020-02-26 23:43:11 +01:00
run: |
esy export-dependencies
if: steps.restore-cache.outputs.cache-hit != 'true'
```
2020-02-14 15:50:11 +01:00
2019-11-05 22:18:49 +01:00
## PHP - Composer
2020-02-14 15:50:11 +01:00
```yaml
2019-11-05 22:18:49 +01:00
- name: Get Composer Cache Directory
id: composer-cache
run: |
echo "::set-output name=dir::$(composer config cache-files-dir)"
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-05 22:18:49 +01:00
with:
path: ${{ steps.composer-cache.outputs.dir }}
key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
restore-keys: |
${{ runner.os }}-composer-
```
2019-11-13 16:55:05 +01:00
## Python - pip
For pip, the cache directory will vary by OS. See https://pip.pypa.io/en/stable/reference/pip_install/#caching
Locations:
- Ubuntu: `~/.cache/pip`
- Windows: `~\AppData\Local\pip\Cache`
- macOS: `~/Library/Caches/pip`
### Simple example
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-13 16:55:05 +01:00
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
Replace `~/.cache/pip` with the correct `path` if not using Ubuntu.
### Multiple OS's in a workflow
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-13 16:55:05 +01:00
if: startsWith(runner.os, 'Linux')
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-13 16:55:05 +01:00
if: startsWith(runner.os, 'macOS')
with:
path: ~/Library/Caches/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-13 16:55:05 +01:00
if: startsWith(runner.os, 'Windows')
with:
path: ~\AppData\Local\pip\Cache
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2020-04-29 20:58:19 +02:00
### Using pip to get cache location
> Note: This requires pip 20.1+
```yaml
- name: Get pip cache dir
id: pip-cache
run: |
echo "::set-output name=dir::$(pip cache dir)"
- name: pip cache
2020-05-26 18:45:38 +02:00
uses: actions/cache@v2
2020-04-29 20:58:19 +02:00
with:
path: ${{ steps.pip-cache.outputs.dir }}
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2019-11-13 16:55:05 +01:00
### Using a script to get cache location
> Note: This uses an internal pip API and may not always work
```yaml
2020-04-29 20:58:19 +02:00
- name: Get pip cache dir
id: pip-cache
run: |
python -c "from pip._internal.locations import USER_CACHE_DIR; print('::set-output name=dir::' + USER_CACHE_DIR)"
2019-11-13 16:55:05 +01:00
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-13 16:55:05 +01:00
with:
path: ${{ steps.pip-cache.outputs.dir }}
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2020-01-22 01:22:40 +01:00
## R - renv
For renv, the cache directory will vary by OS. Look at https://rstudio.github.io/renv/articles/renv.html#cache
Locations:
- Ubuntu: `~/.local/share/renv`
- macOS: `~/Library/Application Support/renv`
- Windows: `%LOCALAPPDATA%/renv`
### Simple example
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-01-22 01:22:40 +01:00
with:
path: ~/.local/share/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
```
Replace `~/.local/share/renv` with the correct `path` if not using Ubuntu.
### Multiple OS's in a workflow
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-01-22 01:22:40 +01:00
if: startsWith(runner.os, 'Linux')
with:
path: ~/.local/share/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-01-22 01:22:40 +01:00
if: startsWith(runner.os, 'macOS')
with:
path: ~/Library/Application Support/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-01-22 01:22:40 +01:00
if: startsWith(runner.os, 'Windows')
with:
path: ~\AppData\Local\renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
```
2020-01-13 00:48:43 +01:00
## Ruby - Bundler
2019-10-31 16:36:50 +01:00
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-10-31 16:36:50 +01:00
with:
path: vendor/bundle
2020-01-13 00:48:43 +01:00
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
2019-10-31 16:36:50 +01:00
restore-keys: |
2020-01-13 00:48:43 +01:00
${{ runner.os }}-gems-
2019-11-01 20:27:43 +01:00
```
2019-11-23 20:13:50 +01:00
When dependencies are installed later in the workflow, we must specify the same path for the bundler.
```yaml
- name: Bundle install
run: |
bundle config path vendor/bundle
bundle install --jobs 4 --retry 3
```
2019-11-01 20:27:43 +01:00
2019-11-04 16:15:02 +01:00
## Rust - Cargo
2020-05-22 00:31:59 +02:00
### Simple end product build
If `Cargo.lock` is checked into git, its hash can be used as a key
to cache filesystem state suitable for the build. Use the `--locked` option
with cargo build and test commands to ensure that the state cached at the
post step corresponds to the contents of `Cargo.lock` that were hashed for
the key.
2019-11-05 17:03:56 +01:00
```yaml
2020-05-21 12:10:26 +02:00
- name: Cache cargo dependencies
uses: actions/cache@v2
2019-11-04 16:15:02 +01:00
with:
2020-05-26 18:45:38 +02:00
path: |
2020-05-21 15:22:09 +02:00
~/.cargo/registry/index
~/.cargo/registry/cache
~/.cargo/git/db
2020-05-21 12:10:26 +02:00
key: cargo-deps-${{ hashFiles('**/Cargo.lock') }}
- name: Cache cargo build
uses: actions/cache@v2
with:
path: target
key: ${{ runner.os }}-cargo-build-${{ hashFiles('**/Cargo.lock') }}
2019-11-04 16:15:02 +01:00
```
2019-11-05 18:04:07 +01:00
2020-05-22 00:31:59 +02:00
### A separate job to fetch and cache the dependencies
The files cached from `$CARGO_HOME` are platform-independent.
If cargo build/test jobs are run on a matrix and `Cargo.lock` changes often,
it might make sense to populate the cache with the matching state in one job,
then reuse it in the matrix jobs.
This example also uses a separate cache to avoid expensive syncs with the
`crates.io-index` repository.
```yaml
jobs:
update-deps:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- id: cargo-deps
name: Cache cargo dependencies
uses: actions/cache@v2
with:
path: |
~/.cargo/registry/index
~/.cargo/registry/cache
~/.cargo/git/db
key: cargo-deps-${{ hashFiles('**/Cargo.lock') }}
- if: ${{ steps.cargo-deps.outputs.cache-hit != 'true' }}
id: ls-crates-io-index
name: Get head commit hash of crates.io registry index
shell: bash
run: |
commit=$(
git ls-remote --heads https://github.com/rust-lang/crates.io-index.git master |
cut -f 1
)
echo "::set-output name=head::$commit"
- if: ${{ steps.cargo-deps.outputs.cache-hit != 'true' }}
name: Cache cargo registry index
uses: actions/cache@v2
with:
path: ~/.cargo/registry/index
key: cargo-index-${{ steps.ls-crates-io-index.outputs.head }}
restore-keys: cargo-index-
- if: ${{ steps.cargo-deps.outputs.cache-hit != 'true' }}
name: Fetch dependencies and update registry index
run: cargo fetch --locked
test:
needs: update-deps
strategy:
matrix:
os: [ubuntu-latest, windows-latest, macos-latest]
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v2
# https://github.com/actions/runner/issues/498
- if: ${{ runner.os == 'Windows' }}
name: Fix up Cargo.lock hash
shell: powershell
run: |
Get-ChildItem . -Recurse -Filter Cargo.lock |
Foreach-Object {
((Get-Content $_.FullName) -join "`n") + "`n" |
Set-Content -NoNewline $_.FullName
}
- name: Restore cargo dependencies
uses: actions/cache@v2
with:
path: |
~/.cargo/registry/index
~/.cargo/registry/cache
~/.cargo/git/db
key: cargo-deps-${{ hashFiles('**/Cargo.lock') }}
- name: Build and test
uses: actions-rs/cargo@v1
2020-06-13 06:03:49 +02:00
env:
CARGO_INCREMENTAL: 0
2020-05-22 00:31:59 +02:00
with:
command: test
args: --locked
```
2020-05-24 05:10:04 +02:00
### Testing a library
Rust library projects typically [do not put][cargo-faq] `Cargo.lock` under
version control. It can be generated with the `cargo generate-lockfile` command
assisted by the registry index cache that is used and possibly updated
for every workflow run. The same index cache is reused by the test jobs.
[cargo-faq]: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
```yaml
jobs:
update-deps:
runs-on: ubuntu-latest
outputs:
crates-io-index-head: ${{ steps.ls-crates-io-index.outputs.head }}
steps:
- uses: actions/checkout@v2
- id: ls-crates-io-index
name: Get head commit hash of crates.io registry index
shell: bash
run: |
commit=$(
git ls-remote --heads https://github.com/rust-lang/crates.io-index.git master |
cut -f 1
)
echo "::set-output name=head::$commit"
- name: Cache cargo registry index
uses: actions/cache@v2
with:
path: ~/.cargo/registry/index
key: cargo-index-${{ steps.ls-crates-io-index.outputs.head }}
restore-keys: cargo-index-
- name: Generate Cargo.lock
run: cargo generate-lockfile
- id: cargo-deps
name: Cache dependency crates
uses: actions/cache@v2
with:
path: ~/.cargo/registry/cache
key: cargo-deps-${{ hashFiles('Cargo.lock') }}
- if: ${{ steps.cargo-deps.outputs.cache-hit != 'true' }}
name: Fetch dependencies
run: cargo fetch --locked
- name: Upload Cargo.lock
uses: actions/upload-artifact@v2
with:
name: lockfile
path: Cargo.lock
test:
needs: update-deps
strategy:
matrix:
os: [ubuntu-latest, windows-latest, macos-latest]
runs-on: ${{ matrix.os }}
2020-06-13 06:03:49 +02:00
env:
CARGO_INCREMENTAL: 0
2020-05-24 05:10:04 +02:00
steps:
- uses: actions/checkout@v2
- name: Download Cargo.lock
uses: actions/download-artifact@v2
with:
name: lockfile
- name: Restore cargo registry index
uses: actions/cache@v2
with:
path: ~/.cargo/registry/index
key: cargo-index-${{ needs.update-deps.outputs.crates-io-index-head }}
# May miss on Windows:
# https://github.com/actions/cache/issues/330#issuecomment-637701649
restore-keys: cargo-index-
- name: Restore dependency crates
uses: actions/cache@v2
with:
path: ~/.cargo/registry/cache
key: cargo-deps-${{ hashFiles('Cargo.lock') }}
- name: Build
uses: actions-rs/cargo@v1
with:
command: build
args: --all-targets --locked
- name: Test
uses: actions-rs/cargo@v1
with:
command: test
args: --locked
```
2020-01-10 23:09:06 +01:00
## Scala - SBT
```yaml
- name: Cache SBT
2020-05-26 18:45:38 +02:00
uses: actions/cache@v2
2020-01-10 23:09:06 +01:00
with:
2020-05-26 18:45:38 +02:00
path: |
~/.ivy2/cache
~/.sbt
2020-01-10 23:09:06 +01:00
key: ${{ runner.os }}-sbt-${{ hashFiles('**/build.sbt') }}
```
2019-11-05 18:04:07 +01:00
## Swift, Objective-C - Carthage
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-05 18:04:07 +01:00
with:
path: Carthage
key: ${{ runner.os }}-carthage-${{ hashFiles('**/Cartfile.resolved') }}
restore-keys: |
${{ runner.os }}-carthage-
```
## Swift, Objective-C - CocoaPods
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2019-11-05 18:04:07 +01:00
with:
path: Pods
key: ${{ runner.os }}-pods-${{ hashFiles('**/Podfile.lock') }}
restore-keys: |
${{ runner.os }}-pods-
```
2020-01-29 17:13:59 +01:00
## Swift - Swift Package Manager
```yaml
2020-05-26 18:45:38 +02:00
- uses: actions/cache@v2
2020-01-29 17:13:59 +01:00
with:
path: .build
key: ${{ runner.os }}-spm-${{ hashFiles('**/Package.resolved') }}
restore-keys: |
${{ runner.os }}-spm-
```