exp push: studio integration

[dberenbaum]

To make exp push/pull more useful, users need to be able to see and manage the exp refs from within Studio (since those exp refs are ignored by GitHub and other Git providers). One of the challenges is that there is not even any trigger by which the Git providers can alert Studio that new exp refs have been pushed.

To enable Studio support for pushed experiments, DVC needs to:

-  [x] Support for saving Studio token to global DVC config or somewhere else that's reasonably secure, persistent, and ideally globally available
- [x] #9163
-  [x] Return links to experiments in Studio so user knows exactly where to see what was pushed - sufficient to return link to project for now
- [x] https://github.com/iterative/dvc/pull/9161
- [x] #9227
- [x] https://github.com/iterative/dvc/pull/9248
- [ ] #9280
- [ ] #9257
- [x] https://github.com/iterative/dvc.org/issues/4440 command ref updates

Blocked/out of scope issues:

- [ ] https://github.com/iterative/dvc/issues/9265
- [ ] https://github.com/iterative/dvc/issues/9295

Related:

• https://github.com/iterative/studio/issues/5050
• https://github.com/iterative/studio/issues/5223
• Sharing experiments vscode-dvc#3077

[mattseddon]

Support for saving Studio token to global DVC config or somewhere else that's reasonably secure, persistent, and ideally globally available

Github CLI has gh auth set of commands. The most useful for me has been gh auth login.

[dberenbaum]

Edited to add:

• Enable live sharing of metrics and exp refs for queued experiments (see studio: STUDIO_REPO_URL needs to be set to live share experiments run from the queue dvclive#485)

[daavoo]

Return links to experiments in Studio so user knows exactly where to see what was pushed

What would this link to? Is it the default project view or something else? Afaik there is no real concept of a view for a single experiment in Studio

[dberenbaum]

What would this link to? Is it the default project view or something else? Afaik there is no real concept of a view for a single experiment in Studio

I think it's discussed in https://github.com/iterative/studio/issues/5150.

• When pushing refs, alert Studio that new ref is available so Studio knows to parse the new refs

See https://github.com/iterative/studio/issues/5273#issuecomment-1462105892. @skshetry Looks like we already have the API needed for this.

[skshetry]

Looks like we already have the API needed for this.

I'll leave that upto the Studio team to decide. :)
At the moment, what we need is a friendly ping to Studio to go and fetch new exp refs and parse. The existing API seems to only use the data from the payload, does not fetch or parse anything other than that. So either a new API or changes to API is needed.

Also there are open questions how Studio should pull new refs. Webhooks don't work for refs.

[skshetry]

Return links to experiments in Studio so user knows exactly where to see what was pushed

This may be a bit tricky with just STUDIO_TOKEN and repo_url to figure out as a user can have multiple views.