-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Conditions are not visualized properly #321
Labels
Comments
yebrahim
changed the title
Conditions is not visulzied properly
Conditions are not visualized properly
Nov 20, 2018
@rileyjbauer, does #293 fix this? |
@yupbank, thanks for filing this. |
the runtime graph that you reach by clicking into a run |
Assuming that this is resolved. Please reopen if anything is outstanding. |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
…code (kubeflow#320) * Create a batch job to allow manual runs of auto-deploying the latest cluster. * * Add a Makefile * Pass in zone. * Move to us-east1-b becasue of kubeflow#321 * Fix zones. * Make zone required.
HumairAK
pushed a commit
to red-hat-data-services/data-science-pipelines
that referenced
this issue
Mar 11, 2024
* add tekton 0.16.3 go mod * update dev setup * update dev docs * update readme * support more argo variable mapping * update feature doc on the list of supported argo variables translation * add task-wise metadata support * add beta whenexpression for condition, unblock runAfter for conditional task * update condition docs * update ui image for tekton-0.16 * Apply suggestions from code review Co-authored-by: Andrew Butler <Andrew.Butler@ibm.com> * address comments and fix conflicts * update doc reference to tekton 0.16 * regenerate tests * updated latest images with tekton 0.16 * regenerate tests Co-authored-by: Andrew Butler <Andrew.Butler@ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the conditions in a pipeline is being visualized as a pod which is wrong
The text was updated successfully, but these errors were encountered: