-
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: add --outs-persist and --outs-persist-no-cache description #217
Conversation
@@ -84,6 +84,17 @@ automatically under DVC control. In case of metrics it's pretty usual because | |||
metric files are small enough to be put into Git or other underlying version | |||
control system. See also the difference between `-o` and `-O` options. | |||
|
|||
* `--outs-persist` - the same as `-o` except outputs will not be removed in case | |||
of [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro) command. |
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.
please, keep the same indent as in the options around
* `--outs-persist` - the same as `-o` except outputs will not be removed in case | ||
of [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro) command. | ||
Upon running [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro), | ||
In case of `-o` target file is removed (if exists) before performing command |
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.
target file is confusing (sounds more like DVC file itself in this context). Why don't we specify that in case of -o
or -O
data files or directories produced in the previous run are removed ... or something like this
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.
Thanks!
Put some comments to improve/fix the doc.
Also:
- Mention where these options are useful. One-two sentence if we can get the from the user request.
- Mention that these options are safe and take care about unprotecting files and that it might affect the performance with certain cache settings (cache=hardlink,symlink?)
- Example - let's not use
foo
,bar
names. Let's come up with something more meaningful. It's hard to understand what's going on when input file isbar
and output isfoo
.
cache types (symlink, hardlink) reproduction step will be prolonged by time | ||
necessary to create copies. `--outs-persist` might still overwrite existing | ||
outputs if `run` command somehow removes existing output (example in | ||
[Examples](#Examples)). |
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.
❤️ I would remove (example in Examples) though
|
||
* Difference between `run --outs` and `run --outs-persist`. | ||
This example shows how using `--outs-persist` influences | ||
reproduction step. |
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.
Can fit into one line?
@shcheklein can we close it for now? |
@pared agreed! |
Related to #1214