-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run-cache: basic docs #2137
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will only be downloaded if --pull
is specified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, --pull
will still try to download using existing lockfiles, even if --no-run-cache
is specified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK then, corrected this a bit. Thanks
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E.g. do we still want a section in run
(or repro
) like this: https://github.com/iterative/dvc.org/pull/1464/files ?
Closes #1289
--run-cache
command optionsrepro --pull
desc.