Skip to content
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 a clarification about --always-changed and "callback" DVC-files #832

Merged
merged 3 commits into from
Dec 17, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions static/docs/command-reference/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,9 +126,11 @@ try creating a pipeline.
- `--ignore-build-cache` - if an exactly equal DVC-file exists (same list of
outputs and inputs, the same command to run), which has been already executed
and is up to date, `dvc run` won't normally execute the command again (thus
"build cache"). This option gives a way to forcefully execute the command
anyway. It's useful if the command is non-deterministic (meaning it produces
different outputs from the same list of inputs).
"build cache"), unless it is an `--always-changed` DVC-file or it doesn't have
any dependencies (same as `--always-changed`). This option gives a way to
jorgeorpinel marked this conversation as resolved.
Show resolved Hide resolved
forcefully execute the command anyway. It's useful if the command is
non-deterministic (meaning it produces different outputs from the same list of
inputs).

- `--remove-outs` - it removes stage outputs before executing the command. If
`--no-exec` specified outputs are removed anyway. This option is enabled by
Expand Down