Skip to content
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

[JENKINS-47974] Last statuses column does not show aborted builds #76

Open
TobiX opened this issue Nov 13, 2017 · 1 comment
Open

[JENKINS-47974] Last statuses column does not show aborted builds #76

TobiX opened this issue Nov 13, 2017 · 1 comment

Comments

@TobiX
Copy link
Contributor

TobiX commented Nov 13, 2017

To reproduce: 

  • create a list view with Compact Column: Statuses w/ Options
  • add a job which can be easily aborted to the view, e.g. this pipeline:
input message: 'Message'
  • abort the build

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
  • assignee: jacob_robertson
  • status: Open
  • priority: Minor
  • resolution: Unresolved
  • imported: 2022-10-30
@TobiX
Copy link
Contributor Author

TobiX commented Jan 5, 2018

marcus_phi:

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant