2019-10-31 23:36:50 +08:00
# Examples
2021-06-01 21:39:29 +08:00
- [C# - NuGet ](#c---nuget )
2022-06-26 03:09:24 +08:00
- [Clojure - Lein Deps ](#clojure---lein-deps )
2021-06-01 21:39:29 +08:00
- [D - DUB ](#d---dub )
- [POSIX ](#posix )
- [Windows ](#windows )
2022-01-16 08:33:29 +08:00
- [Deno ](#deno )
2021-06-01 21:39:29 +08:00
- [Linux ](#linux )
- [macOS ](#macos )
- [Windows ](#windows-1 )
2022-01-16 08:33:29 +08:00
- [Elixir - Mix ](#elixir---mix )
2022-06-06 20:26:51 +08:00
- [Erlang - Rebar3 ](#erlang--rebar3 )
2022-01-16 08:33:29 +08:00
- [Go - Modules ](#go---modules )
- [Linux ](#linux-1 )
- [macOS ](#macos-1 )
- [Windows ](#windows-2 )
2021-06-01 21:39:29 +08:00
- [Haskell - Cabal ](#haskell---cabal )
2022-02-23 02:21:09 +08:00
- [Haskell - Stack ](#haskell---stack )
2023-04-23 17:41:05 +08:00
- [Hugo - Resources ](#hugo---resources )
2021-06-01 21:39:29 +08:00
- [Java - Gradle ](#java---gradle )
- [Java - Maven ](#java---maven )
- [Node - npm ](#node---npm )
- [Node - Lerna ](#node---lerna )
- [Node - Yarn ](#node---yarn )
- [Node - Yarn 2 ](#node---yarn-2 )
- [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 )
- [Multiple OS's in a workflow with a matrix ](#multiple-oss-in-a-workflow-with-a-matrix )
- [Using pip to get cache location ](#using-pip-to-get-cache-location )
- [Python - pipenv ](#python---pipenv )
- [R - renv ](#r---renv )
- [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 )
2022-12-29 21:27:37 +08:00
- [Swift - Mint ](#swift---mint )
2021-04-30 01:58:13 +08:00
- [* - Bazel ](#---bazel )
2019-10-31 23:36:50 +08:00
2019-12-10 08:21:47 +08:00
## C# - NuGet
2021-06-01 21:39:29 +08:00
2019-11-06 01:04:07 +08:00
Using [NuGet lock files ](https://docs.microsoft.com/nuget/consume-packages/package-references-in-project-files#locking-dependencies ):
2019-10-31 23:36:50 +08:00
2019-12-13 09:03:43 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-12-13 09:03:43 +08: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.
2022-03-21 17:01:26 +08:00
With `actions/cache@v3` you can now exclude unwanted packages with [exclude pattern ](https://github.com/actions/toolkit/tree/main/packages/glob#exclude-patterns )
2021-06-01 21:39:29 +08:00
2020-05-27 02:58:07 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-05-27 02:58:07 +08:00
with:
2021-06-01 21:39:29 +08:00
path: |
2020-05-27 02:58:07 +08:00
~/.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.
2023-01-31 18:31:15 +08:00
> **Note** This workflow does not work for projects that require files to be placed in user profile package folder
2021-09-26 20:10:48 +08:00
2019-10-31 23:36:50 +08:00
```yaml
2019-12-10 08:21:47 +08:00
env:
NUGET_PACKAGES: ${{ github.workspace }}/.nuget/packages
steps:
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-12-10 08:21:47 +08:00
with:
path: ${{ github.workspace }}/.nuget/packages
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
2019-10-31 23:36:50 +08:00
```
2022-06-26 03:09:24 +08:00
## Clojure - Lein Deps
```yaml
- name: Cache lein project dependencies
uses: actions/cache@v3
with:
path: ~/.m2/repository
key: ${{ runner.os }}-clojure-${{ hashFiles('**/project.clj') }}
restore-keys: |
${{ runner.os }}-clojure
```
2020-05-11 22:24:05 +08:00
## D - DUB
### POSIX
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-05-11 22:24:05 +08:00
with:
path: ~/.dub
2022-02-12 02:16:52 +08:00
key: ${{ runner.os }}-dub-${{ hashFiles('**/dub.selections.json') }}
2020-05-11 22:24:05 +08:00
restore-keys: |
${{ runner.os }}-dub-
```
### Windows
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-05-11 22:24:05 +08:00
with:
path: ~\AppData\Local\dub
2022-02-12 02:16:52 +08:00
key: ${{ runner.os }}-dub-${{ hashFiles('**/dub.selections.json') }}
2020-05-11 22:24:05 +08:00
restore-keys: |
${{ runner.os }}-dub-
```
2022-01-16 08:33:29 +08:00
## Deno
### Linux
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2022-01-16 08:33:29 +08:00
with:
path: |
~/.deno
~/.cache/deno
key: ${{ runner.os }}-deno-${{ hashFiles('**/deps.ts') }}
```
### macOS
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2022-01-16 08:33:29 +08:00
with:
path: |
~/.deno
~/Library/Caches/deno
key: ${{ runner.os }}-deno-${{ hashFiles('**/deps.ts') }}
```
### Windows
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2022-01-16 08:33:29 +08:00
with:
path: |
~\.deno
2022-03-10 07:44:07 +08:00
~\AppData\Local\deno
2022-01-16 08:33:29 +08:00
key: ${{ runner.os }}-deno-${{ hashFiles('**/deps.ts') }}
```
2019-11-06 01:04:07 +08:00
## Elixir - Mix
2021-04-19 21:42:01 +08:00
2019-10-31 23:36:50 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-10-31 23:36:50 +08:00
with:
2020-11-24 22:52:21 +08:00
path: |
deps
_build
2021-04-20 21:51:44 +08:00
key: ${{ runner.os }}-mix-${{ hashFiles('**/mix.lock') }}
2019-10-31 23:36:50 +08:00
restore-keys: |
2019-11-06 01:04:07 +08:00
${{ runner.os }}-mix-
2019-10-31 23:36:50 +08:00
```
2020-12-29 20:33:30 +08:00
## Erlang - Rebar3
```yaml
- uses: actions/cache@v2
with:
path: |
~/.cache/rebar3
_build
key: ${{ runner.os }}-erlang-${{ env.OTP_VERSION }}-${{ hashFiles('**/*rebar.lock') }}
restore-keys: |
${{ runner.os }}-erlang-${{ env.OTP_VERSION }}-
```
2019-11-06 01:04:07 +08:00
## Go - Modules
2019-11-06 00:03:56 +08:00
2021-06-01 21:39:29 +08:00
### Linux
2019-10-31 23:36:50 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-10-31 23:36:50 +08:00
with:
2021-06-01 21:39:29 +08:00
path: |
~/.cache/go-build
~/go/pkg/mod
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
restore-keys: |
${{ runner.os }}-go-
```
### macOS
2019-10-31 23:36:50 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-10-31 23:36:50 +08:00
with:
2021-06-01 21:39:29 +08:00
path: |
~/Library/Caches/go-build
~/go/pkg/mod
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
restore-keys: |
${{ runner.os }}-go-
```
### Windows
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2021-06-01 21:39:29 +08:00
with:
path: |
2021-09-26 20:05:48 +08:00
~\AppData\Local\go-build
~\go\pkg\mod
2019-11-06 01:04:07 +08:00
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
2019-10-31 23:36:50 +08:00
restore-keys: |
2019-11-06 01:04:07 +08:00
${{ runner.os }}-go-
2019-10-31 23:36:50 +08:00
```
2020-01-11 06:07:52 +08: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-06-19 01:37:50 +08:00
- name: Cache ~/.cabal/packages, ~/.cabal/store and dist-newstyle
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-01-11 06:07:52 +08:00
with:
2020-05-27 00:45:38 +08:00
path: |
~/.cabal/packages
~/.cabal/store
dist-newstyle
2021-12-30 18:54:15 +08:00
key: ${{ runner.os }}-${{ matrix.ghc }}-${{ hashFiles('**/*.cabal', '**/cabal.project', '**/cabal.project.freeze') }}
restore-keys: ${{ runner.os }}-${{ matrix.ghc }}-
```
2020-01-11 06:07:52 +08:00
2022-02-23 02:21:09 +08:00
## Haskell - Stack
2022-06-12 23:45:20 +08:00
### Linux or macOS
2022-02-23 02:21:09 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2022-02-23 02:21:09 +08:00
name: Cache ~/.stack
with:
path: ~/.stack
key: ${{ runner.os }}-stack-global-${{ hashFiles('stack.yaml') }}-${{ hashFiles('package.yaml') }}
restore-keys: |
${{ runner.os }}-stack-global-
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2022-02-23 02:21:09 +08:00
name: Cache .stack-work
with:
path: .stack-work
key: ${{ runner.os }}-stack-work-${{ hashFiles('stack.yaml') }}-${{ hashFiles('package.yaml') }}-${{ hashFiles('**/*.hs') }}
restore-keys: |
${{ runner.os }}-stack-work-
2020-01-11 06:07:52 +08:00
```
2022-06-12 23:45:20 +08:00
### Windows
```yaml
- uses: actions/cache@v3
name: Cache %APPDATA%\stack %LOCALAPPDATA%\Programs\stack
with:
path: |
~\AppData\Roaming\stack
~\AppData\Local\Programs\stack
key: ${{ runner.os }}-stack-global-${{ hashFiles('stack.yaml') }}-${{ hashFiles('package.yaml') }}
restore-keys: |
${{ runner.os }}-stack-global-
- uses: actions/cache@v3
name: Cache .stack-work
with:
path: .stack-work
key: ${{ runner.os }}-stack-work-${{ hashFiles('stack.yaml') }}-${{ hashFiles('package.yaml') }}-${{ hashFiles('**/*.hs') }}
restore-keys: |
${{ runner.os }}-stack-work-
```
2023-04-23 17:41:05 +08:00
## Hugo - Resources
```yaml
- uses: actions/cache@v3
with:
path: resources
key: ${{ runner.os }}-hugo-resources
```
2019-10-31 23:36:50 +08:00
## Java - Gradle
2023-01-31 18:31:15 +08:00
> **Note** Ensure no Gradle daemons are running anymore when your workflow completes. Creating the cache package might fail due to locks being held by Gradle. Refer to the [Gradle Daemon documentation](https://docs.gradle.org/current/userguide/gradle_daemon.html) on how to disable or stop the Gradle Daemons.
2021-05-14 03:40:34 +08:00
2019-10-31 23:36:50 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-10-31 23:36:50 +08:00
with:
2020-07-01 16:30:03 +08:00
path: |
~/.gradle/caches
~/.gradle/wrapper
2021-01-14 05:09:00 +08:00
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }}
2019-10-31 23:36:50 +08:00
restore-keys: |
${{ runner.os }}-gradle-
```
## Java - Maven
```yaml
2020-06-19 01:37:50 +08:00
- name: Cache local Maven repository
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2019-10-31 23:36:50 +08:00
with:
path: ~/.m2/repository
key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
restore-keys: |
2019-11-01 03:08:09 +08:00
${{ runner.os }}-maven-
2019-10-31 23:36:50 +08:00
```
2019-11-06 01:04:07 +08:00
## Node - npm
2019-10-31 23:36:50 +08:00
2021-12-08 18:22:34 +08:00
For npm, cache files are stored in `~/.npm` on Posix, or `~\AppData\npm-cache` on Windows, but it's possible to use `npm config get cache` to find the path on any platform. See [the npm docs ](https://docs.npmjs.com/cli/cache#cache ) for more details.
2019-11-08 10:04:46 +08:00
2020-06-16 03:55:57 +08: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.
2022-12-07 17:25:01 +08:00
After [deprecation ](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ ) of save-state and set-output commands, the correct way to set output is using `${GITHUB_OUTPUT}` . For linux, we can use `${GITHUB_OUTPUT}` whereas for windows we need to use `${env:GITHUB_OUTPUT}` due to two different default shells in these two different OS ie `bash` and `pwsh` respectively.
2020-06-16 03:55:57 +08:00
2023-01-31 18:31:15 +08:00
> **Note** It is not recommended to cache `node_modules`, as it can break across Node versions and won't work with `npm ci`
2019-11-08 10:04:46 +08:00
2022-12-07 17:25:01 +08:00
### **Get npm cache directory using same shell**
### Bash shell
2019-11-08 10:04:46 +08:00
```yaml
2020-03-19 10:05:56 +08:00
- name: Get npm cache directory
2022-12-11 15:19:22 +08:00
id: npm-cache-dir
2022-12-07 17:25:01 +08:00
shell: bash
run: echo "dir=$(npm config get cache)" >> ${GITHUB_OUTPUT}
```
### PWSH shell
```yaml
- name: Get npm cache directory
2022-12-11 15:19:22 +08:00
id: npm-cache-dir
2022-12-07 17:25:01 +08:00
shell: pwsh
run: echo "dir=$(npm config get cache)" >> ${env:GITHUB_OUTPUT}
```
`Get npm cache directory` step can then be used with `actions/cache` as shown below
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-10-14 08:51:53 +08:00
id: npm-cache # use this to check for `cache-hit` ==> if: steps.npm-cache.outputs.cache-hit != 'true'
2019-11-08 10:04:46 +08:00
with:
2020-10-14 08:51:53 +08:00
path: ${{ steps.npm-cache-dir.outputs.dir }}
2019-11-06 01:04:07 +08:00
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
2019-11-06 00:03:56 +08:00
restore-keys: |
2019-11-06 01:04:07 +08:00
${{ runner.os }}-node-
2019-10-31 23:36:50 +08:00
```
2020-04-02 22:35:07 +08:00
## Node - Lerna
```yaml
- name: restore lerna
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-04-02 22:35:07 +08:00
with:
2022-09-29 12:57:49 +08:00
path: '**/node_modules'
2020-04-02 22:35:07 +08:00
key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
```
2019-11-06 01:04:07 +08:00
## Node - Yarn
2019-11-13 23:18:47 +08: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 23:36:50 +08:00
```yaml
2020-02-14 22:50:11 +08:00
- name: Get yarn cache directory path
id: yarn-cache-dir-path
2022-12-26 14:12:18 +08:00
run: echo "dir=$(yarn cache dir)" >> $GITHUB_OUTPUT
2019-11-13 23:18:47 +08:00
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-07-02 21:43:52 +08:00
id: yarn-cache # use this to check for `cache-hit` (`steps.yarn-cache.outputs.cache-hit != 'true'`)
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
```
## Node - Yarn 2
2021-06-01 21:39:29 +08:00
2020-07-02 21:43:52 +08:00
The yarn 2 cache directory will depend on your config. See https://yarnpkg.com/configuration/yarnrc#cacheFolder for more info.
```yaml
- name: Get yarn cache directory path
id: yarn-cache-dir-path
2022-12-26 14:12:18 +08:00
run: echo "dir=$(yarn config get cacheFolder)" >> $GITHUB_OUTPUT
2020-07-02 21:43:52 +08:00
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-02-14 22:50:11 +08:00
id: yarn-cache # use this to check for `cache-hit` (`steps.yarn-cache.outputs.cache-hit != 'true'`)
2019-10-31 23:36:50 +08:00
with:
2020-02-14 22:50:11 +08:00
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
2019-11-13 23:18:47 +08:00
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
2019-10-31 23:36:50 +08:00
restore-keys: |
2019-11-06 01:04:07 +08:00
${{ runner.os }}-yarn-
2019-10-31 23:36:50 +08:00
```
2020-02-27 06:43:11 +08:00
## OCaml/Reason - esy
2021-06-01 21:39:29 +08:00
2020-02-27 06:43:11 +08:00
Esy allows you to export built dependencies and import pre-built dependencies.
```yaml
- name: Restore Cache
id: restore-cache
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-02-27 06:43:11 +08: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
2021-06-01 21:39:29 +08:00
- name: Setting dependency cache
2020-02-27 06:43:11 +08:00
run: |
esy export-dependencies
if: steps.restore-cache.outputs.cache-hit != 'true'
```
2019-11-06 05:18:49 +08:00
## PHP - Composer
2020-02-14 22:50:11 +08:00
```yaml
2019-11-06 05:18:49 +08:00
- name: Get Composer Cache Directory
id: composer-cache
run: |
2022-12-26 14:12:18 +08:00
echo "dir=$(composer config cache-files-dir)" >> $GITHUB_OUTPUT
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-06 05:18:49 +08:00
with:
path: ${{ steps.composer-cache.outputs.dir }}
key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
restore-keys: |
${{ runner.os }}-composer-
```
2019-11-13 23:55:05 +08:00
## Python - pip
For pip, the cache directory will vary by OS. See https://pip.pypa.io/en/stable/reference/pip_install/#caching
Locations:
2021-06-01 21:39:29 +08:00
- Ubuntu: `~/.cache/pip`
- Windows: `~\AppData\Local\pip\Cache`
- macOS: `~/Library/Caches/pip`
2019-11-13 23:55:05 +08:00
### Simple example
2021-06-01 21:39:29 +08:00
2019-11-13 23:55:05 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-13 23:55:05 +08: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
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-13 23:55:05 +08:00
if: startsWith(runner.os, 'Linux')
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-13 23:55:05 +08:00
if: startsWith(runner.os, 'macOS')
with:
path: ~/Library/Caches/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-13 23:55:05 +08:00
if: startsWith(runner.os, 'Windows')
with:
path: ~\AppData\Local\pip\Cache
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2021-01-13 02:29:18 +08:00
### Multiple OS's in a workflow with a matrix
``` yaml
jobs:
build:
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest, macos-latest, windows-latest]
include:
- os: ubuntu-latest
path: ~/.cache/pip
- os: macos-latest
path: ~/Library/Caches/pip
- os: windows-latest
path: ~\AppData\Local\pip\Cache
steps:
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2021-01-13 02:29:18 +08:00
with:
path: ${{ matrix.path }}
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2020-04-30 02:58:19 +08:00
### Using pip to get cache location
2023-01-31 18:31:15 +08:00
> **Note** This requires pip 20.1+
2020-04-30 02:58:19 +08:00
```yaml
- name: Get pip cache dir
id: pip-cache
run: |
2022-12-26 14:12:18 +08:00
echo "dir=$(pip cache dir)" >> $GITHUB_OUTPUT
2020-04-30 02:58:19 +08:00
- name: pip cache
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-04-30 02:58:19 +08:00
with:
path: ${{ steps.pip-cache.outputs.dir }}
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
2020-10-23 08:35:30 +08:00
## Python - pipenv
2019-11-13 23:55:05 +08:00
```yaml
2021-07-16 02:37:10 +08:00
- name: Set up Python
# The actions/cache step below uses this id to get the exact python version
id: setup-python
uses: actions/setup-python@v2
2019-11-13 23:55:05 +08:00
2021-07-16 02:37:10 +08:00
⋮
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-13 23:55:05 +08:00
with:
2020-10-23 08:35:30 +08:00
path: ~/.local/share/virtualenvs
2021-07-16 02:37:10 +08:00
key: ${{ runner.os }}-python-${{ steps.setup-python.outputs.python-version }}-pipenv-${{ hashFiles('Pipfile.lock') }}
2019-11-13 23:55:05 +08:00
```
2020-01-22 08:22:40 +08:00
## R - renv
2021-10-22 22:22:58 +08:00
For renv, the cache directory will vary by OS. The `RENV_PATHS_ROOT` environment variable is used to set the cache location. Have a look at https://rstudio.github.io/renv/reference/paths.html#details for more details.
2020-01-22 08:22:40 +08:00
```yaml
2021-10-22 22:22:58 +08:00
- name: Set RENV_PATHS_ROOT
shell: bash
run: |
echo "RENV_PATHS_ROOT=${{ runner.temp }}/renv" >> $GITHUB_ENV
- name: Install and activate renv
run: |
install.packages("renv")
renv::activate()
shell: Rscript {0}
- name: Get R and OS version
id: get-version
run: |
cat("##[set-output name=os-version;]", sessionInfo()$running, "\n", sep = "")
cat("##[set-output name=r-version;]", R.Version()$version.string, sep = "")
shell: Rscript {0}
- name: Restore Renv package cache
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-01-22 08:22:40 +08:00
with:
2021-10-22 22:22:58 +08:00
path: ${{ env.RENV_PATHS_ROOT }}
key: ${{ steps.get-version.outputs.os-version }}-${{ steps.get-version.outputs.r-version }}-${{ inputs.cache-version }}-${{ hashFiles('renv.lock') }}
restore-keys: ${{ steps.get-version.outputs.os-version }}-${{ steps.get-version.outputs.r-version }}-${{inputs.cache-version }}-
2020-01-22 08:22:40 +08:00
```
2020-01-13 07:48:43 +08:00
## Ruby - Bundler
2020-01-22 08:22:40 +08:00
2021-01-28 19:52:25 +08:00
Caching gems with Bundler correctly is not trivial and just using `actions/cache`
is [not enough ](https://github.com/ruby/setup-ruby#caching-bundle-install-manually ).
2020-01-22 08:22:40 +08:00
2021-01-28 19:52:25 +08:00
Instead, it is recommended to use `ruby/setup-ruby` 's
[`bundler-cache: true` option ](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically )
whenever possible:
2019-10-31 23:36:50 +08:00
```yaml
2021-01-28 19:52:25 +08:00
- uses: ruby/setup-ruby@v1
2019-10-31 23:36:50 +08:00
with:
2021-01-28 19:52:25 +08:00
ruby-version: ...
bundler-cache: true
2019-11-24 03:13:50 +08:00
```
2019-11-02 03:27:43 +08:00
2019-11-04 23:15:02 +08:00
## Rust - Cargo
2019-11-06 00:03:56 +08:00
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-04 23:15:02 +08:00
with:
2020-05-27 00:45:38 +08:00
path: |
2021-05-22 01:41:57 +08:00
~/.cargo/bin/
~/.cargo/registry/index/
~/.cargo/registry/cache/
~/.cargo/git/db/
target/
2020-05-27 00:45:38 +08:00
key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
2019-11-04 23:15:02 +08:00
```
2019-11-06 01:04:07 +08:00
2020-01-11 06:09:06 +08:00
## Scala - SBT
```yaml
- name: Cache SBT
2022-03-21 17:01:26 +08:00
uses: actions/cache@v3
2020-01-11 06:09:06 +08:00
with:
2021-06-01 21:39:29 +08:00
path: |
2020-05-27 00:45:38 +08:00
~/.ivy2/cache
~/.sbt
2020-01-11 06:09:06 +08:00
key: ${{ runner.os }}-sbt-${{ hashFiles('**/build.sbt') }}
```
2019-11-06 01:04:07 +08:00
## Swift, Objective-C - Carthage
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-06 01:04:07 +08:00
with:
path: Carthage
key: ${{ runner.os }}-carthage-${{ hashFiles('**/Cartfile.resolved') }}
restore-keys: |
${{ runner.os }}-carthage-
```
## Swift, Objective-C - CocoaPods
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2019-11-06 01:04:07 +08:00
with:
path: Pods
key: ${{ runner.os }}-pods-${{ hashFiles('**/Podfile.lock') }}
restore-keys: |
${{ runner.os }}-pods-
```
2020-01-30 00:13:59 +08:00
## Swift - Swift Package Manager
```yaml
2022-03-21 17:01:26 +08:00
- uses: actions/cache@v3
2020-01-30 00:13:59 +08:00
with:
path: .build
key: ${{ runner.os }}-spm-${{ hashFiles('**/Package.resolved') }}
restore-keys: |
${{ runner.os }}-spm-
```
2020-07-19 18:52:18 +08:00
## Swift - Mint
```yaml
env:
2022-12-29 21:28:56 +08:00
MINT_PATH: .mint/lib
MINT_LINK_PATH: .mint/bin
2020-07-19 18:52:18 +08:00
steps:
2022-12-29 21:28:56 +08:00
- uses: actions/cache@v3
2020-07-19 18:52:18 +08:00
with:
2022-12-29 21:28:56 +08:00
path: .mint
2020-07-19 18:52:18 +08:00
key: ${{ runner.os }}-mint-${{ hashFiles('**/Mintfile') }}
restore-keys: |
${{ runner.os }}-mint-
```
2021-04-30 01:58:13 +08:00
## * - Bazel
2023-03-13 21:26:31 +08:00
[`bazelisk` ](https://github.com/bazelbuild/bazelisk ) does not have be to separately downloaded and installed because it's already included in GitHub's `ubuntu-latest` and `macos-latest` base images.
2023-03-13 17:52:18 +08:00
### Linux
2021-04-30 01:58:13 +08:00
```yaml
- name: Cache Bazel
2023-03-12 02:40:53 +08:00
uses: actions/cache@v3
2021-04-30 01:58:13 +08:00
with:
path: |
2023-03-13 17:52:18 +08:00
~/.cache/bazel
2023-03-12 02:40:53 +08:00
key: ${{ runner.os }}-bazel-${{ hashFiles('.bazelversion', '.bazelrc', 'WORKSPACE', 'WORKSPACE.bazel', 'MODULE.bazel') }}
restore-keys: |
${{ runner.os }}-bazel-
- run: bazelisk test //...
2021-04-30 01:58:13 +08:00
```
2023-03-12 02:40:53 +08:00
2023-03-13 17:52:18 +08:00
### macOS
```yaml
- name: Cache Bazel
uses: actions/cache@v3
with:
path: |
/private/var/tmp/_bazel_runner/
key: ${{ runner.os }}-bazel-${{ hashFiles('.bazelversion', '.bazelrc', 'WORKSPACE', 'WORKSPACE.bazel', 'MODULE.bazel') }}
restore-keys: |
${{ runner.os }}-bazel-
- run: bazelisk test //...
```