ref: exp-related updates in other to cmds, etc.#2242
Conversation
matching exp push/pull
59412a9 to
a16d83e
Compare
|
Need a review/approval pls 🙂 |
| - `--pull` - [pulls](/doc/command-reference/pull) dependencies and outputs | ||
| involved in the stages being reproduced, if they are found in the | ||
| [default remote storage](/doc/command-reference/remote/default). Note that it | ||
| tries the local run-cache first (unless `--no-run-cache` is also used). | ||
| - `--pull` - downloads dependencies and outputs in the stages being reproduced | ||
| from the [default remote storage](/doc/command-reference/remote/default) (see | ||
| `dvc pull`) based on the run-cache. Note that this doesn't include initial | ||
| pipeline data sources (never found in the run-cache). |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
p.s. it's a kind of confusing option. Why is --pull specifically related to run-cache? 🤷 But anyway, when treeverse/dvc/issues/4742 is addressed, that should be taken care of.
There was a problem hiding this comment.
likely just because the original request was just for a method to pull run-cache+outputs for specific (run-cached) stages: treeverse/dvc#4223
There was a problem hiding this comment.
I think we should probably not use dependencies here at all. Maybe just say something like this?
[pulls](...) outputs for any stages which restored from [run-cache](/doc/user-guide/experiment-management#automatic-log-of-stage-runs-run-cache) during pipeline reproduction. Outputs will be pulled from the [default remote storage](...).
There was a problem hiding this comment.
Good call. Updated 👍
Matches certain changes in #2200 and #2243 (mainly for consistency in terminology, structure, etc.).
masterbefore merging (after ref: remaining exp cmds (branch,res,list,push,pull,gc) #2243).