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: _docs/pipelines/pipeline-caching.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,7 @@ This means that unlike other CI solutions where you have to manually describe wh
200
200
The main choice that you have is which files to place on the volume. For example, Node.js uses the folder`node_modules` for its dependencies which are placed under the project folder[which is automatically placed under the volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#cloning-the-source-code). So all contents of`node_modules` will be cached by default without any further action on your part.
201
201
202
202
>**NOTE**
203
-
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/codefresh-on-prem/), this kind of caching is not available for the built-in runtime.<br>You need to use the[Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) with your own runtime to activate volume caching.
203
+
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/installation-options/on-premises/), this kind of caching is not available for the built-in runtime.<br>You need to use the[Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) with your own runtime to activate volume caching.
204
204
205
205
The simplest way to see this caching mechanism in action is this pipeline: