Sharing multiple experiments

[dberenbaum]

dvc exp push and dvc exp pull each take a single experiment. The experiments command is all about running multiple experiments, so most real-world use cases will involve wanting to push or pull multiple (or even all) experiments. For the initial proof of concept, it made sense to focus on one, but there should be ways to share multiple experiments at once. This could include:

• Specifying a list of experiment IDs
• Combining with exp list to get a particular subset of experiments to share
• Sharing all experiments in a branch
• Sharing all experiments from a given parent commit
• Sharing all experiments for the last n commits

[dberenbaum]

Related (duplicate?): #4649

[dberenbaum]

Seems like this could be handled using flags similar to those found in other dvc commands already:

  -w, --workspace       Push experiments derived from the current workspace.
  -a, --all-branches    Push experiments derived from the tip of all Git branches.
  -T, --all-tags        Push experiments derived from all Git tags.
  -A, --all-commits     Push experiments derived from all Git commits.

The same options could probably apply dvc exp list.

[dberenbaum]

@pmrowla Are there any issues or complications with pushing multiple experiments that are different from pushing a single experiment?

[pmrowla]

@dberenbaum the complication is regarding how to handle conflicts. I suppose if --force is given we can just assume the user wants to force push everything, but if --force is not used, do we abort as soon as there is any conflict, or do we behave like dvc push and continue trying to push everything else?

[dberenbaum]

A user requested this in https://discord.com/channels/485586884165107732/485596304961962003/895329378110677003.

A workaround for now is dvc exp list --names-only | xargs -n 1 dvc exp push origin.

[dberenbaum]

Moving the priority of this up since we are promoting the collaborative aspect of experiment versioning.