You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also think this should be improved. With pipelines, for us (and many other I guess), aborted builds are much more common and 'natural' status of a job, since it's what's you get if you manually stop a pipeline from running all the way to production with an input step. So I think Aborted should be treated as a status like the other.
However, it's not at all obvious how this status fit in the ordering. Where in the list: S{{uccess > Unstable > Failed}} does it fit?
Between Success and Unstable? That would mean it's an "improvement" to go from Unstable to Aborted. That is a bit weird.
Between Unstable and Failed? That would mean it's an "improvement" to go from Failed to Aborted, and from Aborted to Unstable. Maybe that makes more sense.
Maybe some other Jenkins functionality has established a convention?
I actually think a part of the problem is that we can't distinguish between an abort due to an error and an abort due to a "business decision".
To reproduce:
input message: 'Message'
The aborted builds do not show up in the status column.
Originally reported by jl68, imported from: Last statuses column does not show aborted builds
The text was updated successfully, but these errors were encountered: