blog: collaborative experiments post

[flippedcoder]

Tentative publish date: 09/21/2021

This blog post is an example of sharing experiments using DVC remotes. It's different from this user guide because it walks through an example of remotes being used in a project flow instead of reference material for setting up and working with remotes.

[dberenbaum]

Looks good!

Are users supposed to be able to pull your experiments, or are those just illustrative examples? It's a little unclear where users are expected to be able to follow along and where that might not work.

Also, it might be worth sharing with @iesahin. I know he's been working on the docs for sharing experiments, so maybe it's helpful to compare and decide what belongs in the blog post vs. the docs.

[iesahin]

I believe a stronger language is better here.

[iesahin]

A link to https://dvc.org/doc/command-reference/remote/add#supported-storage-types might be good here.

[iesahin]

Could we use example-dvc-experiments for this blog post instead of https://github.com/iterative/dvc-learn-project ?

[flippedcoder]

Could we use example-dvc-experiments for this blog post instead of https://github.com/iterative/dvc-learn-project ?

Sure. I don't see why not!

[flippedcoder]

@iesahin Just a question about the https://github.com/iterative/example-dvc-experiments repo.
Would people following along with the blog post be able to push and pull from the remote in the DVC config? Just checking to see how I should update the post.

[flippedcoder]

Hi @iesahin! I've made the updates you mentioned, but now I have a question. When I run dvc exp list origin --all in the example-dvc-experiments repo, nothing is returned. Is that expected behavior?

[iesahin]

Thank you @flippedcoder Normally, dvc exp list should list the experiments in the repository, but we have a bug (iterative/dvc#6920) that prevented me to upload the experiments to the newly generated repository. I'm waiting for the new release (2.8.4). I'll upload the experiments and you'll be able to list them with dvc exp list.

I'll read the post now, thank you.

[iesahin]

I can't see a deployment. What's up? @shcheklein

[iesahin]

Thank you @flippedcoder That's very clear and to the point. I think adding another step to fork our repo makes it more realistic. Details are in the comments.

[jendefig]

I can't see a deployment. What's up? @shcheklein

I have same question.

[flippedcoder]

@julieg18 or @rogermparent Not sure if y'all are the right people to ask, but do y'all have any insight on why the deployment isn't re-triggering? I've merged with master so all of the most recent changes are on this branch.

[julieg18]

@julieg18 or @rogermparent Not sure if y'all are the right people to ask, but do y'all have any insight on why the deployment isn't re-triggering? I've merged with master so all of the most recent changes are on this branch.

Normally heroku will redeploy an app once we push a an update to a branch. But Heroku is also configured to destroy an app after 30 days of inactivity. What I think might have happened is Heroku deleted this app after 30 days of inactivity and didn't attempt to create a new app even after the branch started getting new changes again. What do you think @rogermparent?

[rogermparent]

What I think might have happened is Heroku deleted this app after 30 days of inactivity and didn't attempt to create a new app even after the branch started getting new changes again. What do you think @rogermparent?

I think you're exactly right, I'm pretty certain I've seen this happen before after Heroku cleans up an old review app. I've also seen manual deployments like the one Julie just did behave oddly, so this PR may run into something like that in the future if another commit is added to this PR.

[flippedcoder]

Thanks @julieg18 and @rogermparent! If any more changes need to be made, I'll probably just close this PR and open another.

[flippedcoder]

@jendefig @iesahin You can take a look at the most recent deploy now!

[julieg18]

Thanks @julieg18 and @rogermparent! If any more changes need to be made, I'll probably just close this PR and open another.

Now that the app has been rebuilt and it hasn't been thirty days, pushing changes to this branch should trigger a automatic rebuild. But if it doesn't, feel free to do that!

[rogermparent]

I should clarify that I only brought up further PRs causing problems just in case it happens, it's totally fine to update in the normal way and just reach out again if an issue occurs.

[iesahin]

Thank you @flippedcoder. That's a very clear and to-the-point post.