Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use "Start" for runs, "Create" for experiments #649

Closed
rileyjbauer opened this issue Jan 8, 2019 · 2 comments · Fixed by #650
Closed

Use "Start" for runs, "Create" for experiments #649

rileyjbauer opened this issue Jan 8, 2019 · 2 comments · Fixed by #650
Assignees
@rileyjbauer
Labels
area/frontend

Comments

@rileyjbauer
Copy link
Contributor

Runs are active upon creation, so the verb "start" makes more sense.

No action is taken upon creation of Experiments, so the verb "create" makes more sense (than "start").
@rileyjbauer
Copy link
Contributor Author

/area front-end
/assign rileyjbauer

@rileyjbauer
Copy link
Contributor Author

To clarify, "Start" should be used at the end of the "create run" flow, the toolbar buttons can continue to say "Create"

@rileyjbauer rileyjbauer mentioned this issue Jan 8, 2019
Merged
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
@terrytangyuan
Fix paths to license tool scripts (kubeflow#649)
5b04a98
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
@janeman98
Enabled test_sklearn.py, test_tensorflow.py, test_xgboost.py, test_tr…
ed58014 
…ansformer.py to run in an env without ext load balancer (kubeflow#649)
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
@animeshsingh
add mlx-reference (kubeflow#649)
3163801
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rileyjbauer rileyjbauer

Labels
area/frontend
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use "create" rather than "start" except when initiating a run rileyjbauer/pipelines
2 participants
@k8s-ci-robot @rileyjbauer