Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28552

visible claimed failure reason in build result

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • claim-plugin
    • None
    • Jenkins 1.613, claim-plugin 2.7

      So far the claimed failure reason is not visible in the build result, it was put into img's title only.

      see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly

      As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

      And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

      Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.

          [JENKINS-28552] visible claimed failure reason in build result

          Larry Cai created issue -
          Larry Cai made changes -
          Description Original: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          {{<img width="16" height="16"
                   title="${%claimed.reason(it.claimedByName,it.reason)}"
            src="${imagesURL}/16x16/lock.gif"/>}}

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          New: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          {quote}<img width="16" height="16"
                   title="${%claimed.reason(it.claimedByName,it.reason)}"
            src="${imagesURL}/16x16/lock.gif"/>{quote}

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          Larry Cai made changes -
          Description Original: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          {quote}<img width="16" height="16"
                   title="${%claimed.reason(it.claimedByName,it.reason)}"
            src="${imagesURL}/16x16/lock.gif"/>{quote}

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          New: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          {{<img width="16" height="16" title="${%claimed.reason(it.claimedByName,it.reason)}" src="${imagesURL}/16x16/lock.gif"/>}}

          see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          Larry Cai made changes -
          Description Original: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          {{<img width="16" height="16" title="${%claimed.reason(it.claimedByName,it.reason)}" src="${imagesURL}/16x16/lock.gif"/>}}

          see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          New: So far the claimed failure reason is not visible in the build result, it was put into img's title only.

          see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly

          As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail

          And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.

          Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
          Larry Cai made changes -
          Summary Original: visible reason in build result New: visible claimed failure reason in build result
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163397 ] New: JNJira + In-Review [ 181219 ]
          Arnaud TAMAILLON made changes -
          Assignee Original: Christian Bremer [ ki82 ] New: Arnaud TAMAILLON [ greybird ]

            greybird Arnaud TAMAILLON
            larrycai Larry Cai
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: