run-cache: basic docs#2137
Conversation
| - `--pull` - [pulls](/doc/command-reference/pull) dependencies and outputs | ||
| involved in the stages being reproduced, if they are found in the | ||
| [default](/doc/command-reference/remote/default) remote storage. Note that it | ||
| checks the local run-cache too (available history of stage runs). | ||
| [default remote storage](/doc/command-reference/remote/default). Note that it | ||
| tries the local run-cache first. | ||
|
|
||
| > Has no effect if combined with `--no-run-cache`. |
There was a problem hiding this comment.
There was a problem hiding this comment.
It will only be downloaded if --pull is specified.
There was a problem hiding this comment.
Right. But I meant if --pull is used WITH --no-run-cache, while there's no run-cache, --pull still does something? The way this is written now indicates that --no-run-cache somehow cancels all effects of --pull.
There was a problem hiding this comment.
Yes, --pull will still try to download using existing lockfiles, even if --no-run-cache is specified.
There was a problem hiding this comment.
OK then, corrected this a bit. Thanks
jorgeorpinel
force-pushed
the
run-cache
branch
from
9f50421 to
71b9c23
Compare
| ### Run-cache | ||
|
|
||
| `dvc repro` and `dvc run` by default populate and reutilize a log of stages that | ||
| have been run in the project. It is found in the `runs/` directory inside the | ||
| cache (or [remote storage](/doc/command-reference/remote)). |
There was a problem hiding this comment.
Other than in the DVC Internals guide should this be elsewhere?
If anyone can think of scenarios/examples/how-tos we should consider to mention the run-cache please lmk.
There was a problem hiding this comment.
E.g. do we still want a section in run (or repro) like this: https://github.com/iterative/dvc.org/pull/1464/files ?
3 participants
Closes #1289
--run-cachecommand optionsrepro --pulldesc.