-
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
Will pipelines support the same behavior as argo retry
#1198
Comments
/assign @vicaire |
Yes, we can support this if it is not already supported. Would you like to contribute the change? |
I'd like to contribute! |
I have assigned this item to you. Thanks! |
@cheyang May I ask, is there any progress about this feature? |
I didn't have chance to work on it. @xiaogaozi , if you'd like to pick it, it will be great. Thanks. |
#1720 should cover it. |
Is it possible to use the retry the pipeline API (#1720) from kfp? If not, is there a way to retry pipeline like |
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. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
* Add github action for new images * Update configmap for 0.5 * Generate v0.5.0 rc0 manifest * Add github action for new images * Update configmap for 0.5 * Generate v0.5.0 rc0 manifest * Update release yaml * Update multi model server flag * Add triton check for MMS * fix version * Fix pmml release version * Remove ephemeralContainers * Update 0.5.0-rc0 yaml * Remove KFS version check for quick install * Rename pmml-docker-publiish.yml to pmml-docker-publish.yml
I'm wondering if
pipelines
will support the behavior ofargo retry
. The benefit of doing this is to avoid rerun the successful step, only starting from the failed step without the end user input.The text was updated successfully, but these errors were encountered: