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

Run trigger doc is vague #746

Closed
haresh-chudgar opened this issue May 31, 2019 · 8 comments
Closed

Run trigger doc is vague #746

haresh-chudgar opened this issue May 31, 2019 · 8 comments
Labels
area/docs doc-sprint Issues to work on during the Kubeflow Doc Sprint kind/bug lifecycle/stale priority/p2

Comments

@haresh-chudgar
Copy link

The Run trigger documentation references a flag but there's no documentation on how that flag should be set in the pipeline and no examples are linked.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.80. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@sarahmaddox
Copy link
Contributor

I think this is the page that the issue refers to:
https://www.kubeflow.org/docs/pipelines/concepts/run-trigger/

@sarahmaddox sarahmaddox added the doc-sprint Issues to work on during the Kubeflow Doc Sprint label Jun 3, 2019
@discordianfish
Copy link
Member

Yes, it's unclear to me as well how this is suppose to work and I can't find an example in https://github.com/kubeflow/examples either.

@discordianfish
Copy link
Member

Related: ScheduledWorkflow isn't documented in general. I assume the run-trigger is part of that: https://github.com/kubeflow/pipelines/blob/578e8231d01074b9dbe40ace1db8cc444a6a1bd8/backend/src/crd/pkg/apis/scheduledworkflow/v1beta1/types.go

@jtfogarty
Copy link

/area docs
/priority p2

@stale
Copy link

stale bot commented Apr 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@discordianfish
Copy link
Member

This relevant

@stale stale bot removed the lifecycle/stale label Apr 20, 2020
@stale
Copy link

stale bot commented Jul 19, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this as completed Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs doc-sprint Issues to work on during the Kubeflow Doc Sprint kind/bug lifecycle/stale priority/p2
Projects
None yet
Development

No branches or pull requests

5 participants