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.

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

User should be able to create a new Recurring Run from the pipeline page. #54

Closed
Ark-kun opened this issue Nov 5, 2018 · 2 comments
Closed

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Nov 5, 2018

No description provided.

@yebrahim
Copy link
Contributor

yebrahim commented Nov 6, 2018

I'm not sure how useful this would be. I think you'll want to try things out in an experiment first before creating a recurring run out of a pipeline.
/cc @ajayalfred.

@yebrahim yebrahim changed the title User should be able to create a new Scheduled Job from the pipeline page. User should be able to create a new Recurring Run from the pipeline page. Nov 6, 2018
@ajayalfred
Copy link
Contributor

Agree. The intent behind actions on the pipeline page is to guide the user through the process of experimenting with runs and then moving on to recurring runs. It is unlikely a user will want to create a recurring run directly from the pipeline without experimenting with single runs.

Once we have filtering, the user will be able to navigate directly to past runs and experiments and use them to create recurring runs.

@yebrahim yebrahim closed this as completed Dec 4, 2018
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
HumairAK referenced this issue in red-hat-data-services/data-science-pipelines Mar 11, 2024
Fix: Adding default-configs overlay to the CI kfdef
HumairAK added a commit to HumairAK/data-science-pipelines that referenced this issue Jun 20, 2024
UPSTREAM: <carry>: Upgrade DSP api/go.mod package versions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants