From db4dd62e75f571bc7bb6818b20a5c77d6e4442d9 Mon Sep 17 00:00:00 2001 From: Ruslan Kuprieiev Date: Tue, 3 Dec 2019 19:56:39 +0200 Subject: [PATCH] run: add a clarification about --always-changed and "callback" DVC-files Fixes https://github.com/iterative/dvc/issues/2843 --- static/docs/command-reference/run.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/static/docs/command-reference/run.md b/static/docs/command-reference/run.md index 06180fa5fe..2986da9632 100644 --- a/static/docs/command-reference/run.md +++ b/static/docs/command-reference/run.md @@ -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 + 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