-
Notifications
You must be signed in to change notification settings - Fork 104
/retest
should only re-run failed pipelines
#1811
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
Comments
That's a good point but unfortunately this ship has sailed since we can't change the default behavior, we can tho introduce a /retest failed (assuming there is no PR named failed) |
to overcome the problem with potential names I guess a new comment like |
added this jira issue https://issues.redhat.com/browse/SRVKP-7236 so we can track this internally |
we can keep #1959 |
@chmouel is this issue actually the same as that one? This one is more about re-running failed pipelines without re-running them all or listing each individually while the other issue is more about an expected behavior / bug |
Uh oh!
There was an error while loading. Please reload this page.
If a few pipelines are failing, there is no way for us to re-test only the failed ones.
Restarting all of them is a waste of resources and increases the chance of getting transient errors on pipelines (registry temporarily down, etc)
This would be similar to how Prow works: https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md
The text was updated successfully, but these errors were encountered: