-
Improvement
-
Resolution: Fixed
-
Major
-
-
v1.9
The build status indicator does not seem to distinguish between Failed and Aborted builds.
For instance, currently (22:20 EST on 22 Aug 2013), the build status icon for jclouds-cli[1] shows up as failing, when the status of the last build is actually "Aborted" [2].
Would it make sense to add an option to treat Aborted as its own state, or indeed to make that the default behaviour?
Any pointers as to where in a the code a change would need to be made to make this work?
[1] http://incubator.apache.org/projects/jclouds.html
[2] https://jclouds.ci.cloudbees.com/job/jclouds-cli/28/
[JENKINS-19319] Distinguish between Aborted and Failed in the status icon
Andrew Phillips
added a comment - > might be useful to see where the different build states are mapped to
> images in the code.
Indeed it is. Thanks, mgedmin!
Andrew Phillips
added a comment - > might be useful to see where the different build states are mapped to
> images in the code.
Indeed it is. Thanks, mgedmin ! Code changed in jenkins
User: Julian Junghans
Path:
src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java
src/main/webapp/status/build-aborted-lightgrey-flat.svg
src/main/webapp/status/build-aborted-lightgrey.svg
http://jenkins-ci.org/commit/embeddable-build-status-plugin/5917f4ce03283c6bade372811bb80b2c46adc865
Log:
suggested solution for: JENKINS-19319 Distinguish between Aborted and Failed in the status icon
Code changed in jenkins
User: Marius Gedminas
Path:
src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java
src/main/webapp/status/build-aborted-lightgrey-flat.svg
src/main/webapp/status/build-aborted-lightgrey.svg
http://jenkins-ci.org/commit/embeddable-build-status-plugin/4eb5bd32d2a822f87dca70d1fad9eca6e15d2266
Log:
Merge pull request #16 from DerJJ/master
JENKINS-19319 Distinguish between Aborted and Failed in the status icon
Compare: https://github.com/jenkinsci/embeddable-build-status-plugin/compare/48167d517886...4eb5bd32d2a8
https://github.com/jenkinsci/embeddable-build-status-plugin/pull/5/files might be useful to see where the different build states are mapped to images in the code.