You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,11 @@ The file or folder to cache.
32
32
33
33
The maximum caching level to restore, if available. See [the available caching levels](#caching-levels)
34
34
35
-
#### `save` (string, specific values)
35
+
#### `save` (string or array of strings, specific values)
36
36
37
-
The level to use for saving the cache. See [the available caching levels](#caching-levels)
37
+
The level(s) to use for saving the cache. See [the available caching levels](#caching-levels).
38
+
39
+
You can specify multiple levels in an array to save the same artifact as a cache for all those levels.
38
40
39
41
## Options
40
42
@@ -118,7 +120,7 @@ You can always have more complicated logic by using the plugin multiple times wi
118
120
* second step:
119
121
- will restore the file-level cache of the `node_modules` folder saved by the first step and run `npm test`
120
122
* third step (that will only run on the `master` branch):
121
-
- will restore the file-level cache saved by the first step, run `npm run deploy` and finally save the contents of the `node_modules` folder as a pipeline-level cache for usage as a basis even when the lockfile changes (in the first step)
123
+
- will restore the file-level cache saved by the first step, run `npm run deploy` and finally save the contents of the `node_modules` folder as both a pipeline-level and global (all-level) cache for usage as a basis even when the lockfile changes (in the first step)
0 commit comments