usage: dvc exp push [-h] [-q | -v] [-f] [--no-cache] [-r <name>] [-j <number>] [--run-cache] git_remote experiment positional arguments: git_remote Git remote name or Git URL experiment Experiment to push
git fetchdon't work with
dvc experimentsbecause these are saved under custom Git references. See How does DVC track experiments? in
dvc exp runto learn more about DVC experiment storage.
git_remote name (e.g.
origin) or Git URL is required, as well as
experiment name or hash (see
dvc exp run) to push.
The first action of
dvc exp push is to upload the
experiment to the Git
remote so it can be pulled later from other repo clones (equivalent to
git push <git_remote> refs/exps/<experiment>). Use
dvc exp list <git_remote>
to see experiments in the remote.
This command will also try to push all
cached data associated with the experiment to DVC
remote storage, unless
--no-cache is used.
The default remote is used (see
dvc remote default) unless a specific one is
--force- rewrite the
experimentcommit if it already exists in the Git remote. Equivalent to
git push --force(rewrites history)
--no-cache- do not push cached files associated with this experiment to a DVC remote.
--remote <name>- name of the
dvc remoteto push cached files to.
--run-cache- uploads all available history of stage runs to the
--jobs <number>- parallelism level for DVC to upload data to remote storage. The default value is
4 * cpu_count(). For SSH remotes, the default is
4. Note that the default value can be set using the
jobsconfig option with
dvc remote modify. Using more jobs may improve the overall transfer speed.
--help- shows the help message and exit.
--quiet- do not write anything to standard output. Exit with 0 if no problems arise, otherwise 1.
--verbose- displays detailed tracing information from executing the
This example is based on our Get Started, where you can find the actual source code.
Let's say we have run 3 experiments in our project:
$ dvc exp list --all 11-bigrams-experiment: exp-e6c97 exp-1dad0 exp-1df77
We would now like to share one of them with others via the Git remote:
$ dvc exp push origin exp-e6c97 Pushed experiment 'exp-e6c97' to Git remote 'origin'.
We can now see that the experiment exists in the remote repo:
$ dvc exp list --all origin master: exp-e6c97