-
Notifications
You must be signed in to change notification settings - Fork 105
[JENKINS-60507] Eventually cancel node blocks in anomalous status
#299
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
Conversation
|
Probably too aggressive, trying to tune this a bit. Without knowing how to reproduce the original problem I can only guess. |
…us twice in a row
Absolutely interested ! |
Co-authored-by: Hervé Le Meur <[email protected]>
|
@jglick just installed on ci.jenkins: Let's check how ti behaves. |
That there are no builds marked aborted improperly. If this works, it should automatically clean up certain cases of builds which were actually corrupted (letting them complete normally if |
|
I guess there have been no obvious problems arising from this? So I think it could be merged. |
Confirmed. Sorry for the delay in answer, but no issue: go go go |

Observed during a build of jenkinsci/bom#1832. @dduportal et al., any interest in testing this?