2019-10-17 17:53:03 +02:00
# cache
2019-10-30 19:48:49 +01:00
2020-01-14 16:11:41 +01:00
This action allows caching dependencies and build outputs to improve workflow execution time.
2019-10-30 19:48:49 +01:00
2019-11-15 21:04:12 +01:00
< a href = "https://github.com/actions/cache/actions?query=workflow%3ATests" > < img alt = "GitHub Actions status" src = "https://github.com/actions/cache/workflows/Tests/badge.svg?branch=master&event=push" > < / a >
2019-10-31 15:37:00 +01:00
2019-11-05 20:09:13 +01:00
## Documentation
See ["Caching dependencies to speed up workflows" ](https://help.github.com/github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows ).
2019-10-30 19:48:49 +01:00
## Usage
### Pre-requisites
Create a workflow `.yml` file in your repositories `.github/workflows` directory. An [example workflow ](#example-workflow ) is available below. For more information, reference the GitHub Help Documentation for [Creating a workflow file ](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file ).
### Inputs
* `path` - A directory to store and save the cache
* `key` - An explicit key for restoring and saving the cache
* `restore-keys` - An ordered list of keys to use for restoring the cache if no cache hit occurred for key
### Outputs
* `cache-hit` - A boolean value to indicate an exact match was found for the key
> See [Skipping steps based on cache-hit](#Skipping-steps-based-on-cache-hit) for info on using this output
### Example workflow
```yaml
2019-11-08 03:04:46 +01:00
name: Caching Primes
2019-10-30 19:48:49 +01:00
on: push
jobs:
build:
runs-on: ubuntu-latest
2019-12-23 16:30:34 +01:00
2019-10-30 19:48:49 +01:00
steps:
- uses: actions/checkout@v1
2019-11-08 03:04:46 +01:00
- name: Cache Primes
id: cache-primes
2019-11-04 22:40:33 +01:00
uses: actions/cache@v1
2019-10-30 19:48:49 +01:00
with:
2019-11-08 03:04:46 +01:00
path: prime-numbers
key: ${{ runner.os }}-primes
2019-10-30 19:48:49 +01:00
2019-11-08 03:04:46 +01:00
- name: Generate Prime Numbers
if: steps.cache-primes.outputs.cache-hit != 'true'
run: /generate-primes.sh -d prime-numbers
2019-12-23 16:30:34 +01:00
2019-11-08 03:04:46 +01:00
- name: Use Prime Numbers
run: /primes.sh -d prime-numbers
2019-10-30 19:48:49 +01:00
```
2019-12-08 00:25:23 +01:00
## Implementation Examples
2019-12-23 16:30:34 +01:00
Every programming language and framework has its own way of caching.
2019-12-08 00:25:23 +01:00
See [Examples ](examples.md ) for a list of `actions/cache` implementations for use with:
- [C# - Nuget ](./examples.md#c---nuget )
- [Elixir - Mix ](./examples.md#elixir---mix )
- [Go - Modules ](./examples.md#go---modules )
2020-01-10 23:07:52 +01:00
- [Haskell - Cabal ](./examples.md#haskell---cabal )
2019-12-08 00:25:23 +01:00
- [Java - Gradle ](./examples.md#java---gradle )
- [Java - Maven ](./examples.md#java---maven )
- [Node - npm ](./examples.md#node---npm )
2020-04-02 16:35:07 +02:00
- [Node - Lerna ](./examples.md#node---lerna )
2019-12-08 00:25:23 +01:00
- [Node - Yarn ](./examples.md#node---yarn )
2020-02-26 23:43:11 +01:00
- [OCaml/Reason - esy ](./examples.md##ocamlreason---esy )
2019-12-08 00:25:23 +01:00
- [PHP - Composer ](./examples.md#php---composer )
- [Python - pip ](./examples.md#python---pip )
2020-01-22 01:22:40 +01:00
- [R - renv ](./examples.md#r---renv )
2020-01-13 00:48:43 +01:00
- [Ruby - Bundler ](./examples.md#ruby---bundler )
2019-12-08 00:25:23 +01:00
- [Rust - Cargo ](./examples.md#rust---cargo )
2020-01-10 23:09:06 +01:00
- [Scala - SBT ](./examples.md#scala---sbt )
2019-12-08 00:25:23 +01:00
- [Swift, Objective-C - Carthage ](./examples.md#swift-objective-c---carthage )
- [Swift, Objective-C - CocoaPods ](./examples.md#swift-objective-c---cocoapods )
2020-01-29 17:13:59 +01:00
- [Swift - Swift Package Manager ](./examples.md#swift---swift-package-manager )
2019-10-31 15:45:47 +01:00
2019-10-30 19:48:49 +01:00
## Cache Limits
2020-02-05 16:33:21 +01:00
A repository can have up to 5GB of caches. Once the 5GB limit is reached, older caches will be evicted based on when the cache was last accessed. Caches that are not accessed within the last week will also be evicted.
2019-10-30 19:48:49 +01:00
## Skipping steps based on cache-hit
Using the `cache-hit` output, subsequent steps (such as install or build) can be skipped when a cache hit occurs on the key.
Example:
```yaml
steps:
2020-03-18 14:44:24 +01:00
- uses: actions/checkout@v2
2019-10-30 19:48:49 +01:00
2019-11-04 22:40:33 +01:00
- uses: actions/cache@v1
2019-10-30 19:48:49 +01:00
id: cache
with:
path: path/to/dependencies
2019-11-12 21:33:22 +01:00
key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}
2019-12-23 16:30:34 +01:00
2019-10-30 19:48:49 +01:00
- name: Install Dependencies
if: steps.cache.outputs.cache-hit != 'true'
run: /install.sh
```
2019-10-31 17:06:17 +01:00
> Note: The `id` defined in `actions/cache` must match the `id` in the `if` statement (i.e. `steps.[ID].outputs.cache-hit`)
2019-10-30 19:48:49 +01:00
## Contributing
We would love for you to contribute to `@actions/cache` , pull requests are welcome! Please see the [CONTRIBUTING.md ](CONTRIBUTING.md ) for more information.
## License
2019-10-31 15:37:00 +01:00
The scripts and documentation in this project are released under the [MIT License ](LICENSE )