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

Make it clear when current run broke the build

    • 1.0-japan-m9

      A common question asked when using CI is "did something change to break this build", not just who broke it (blame dark pattern) or where it was broken (which is already clear with stage graph).

      1. Calling out that this specific run is where the build broke (ie previously it was ok) may invite users to look at the change (it is something I commonly do, after looking at the failure message)
      2. For any failed view, it may be wise to have a quick link back to the last successful run.

          [JENKINS-35806] Make it clear when current run broke the build

          James Dumay created issue -
          Michael Neale made changes -
          Workflow Original: Problems April 2016 v2 [ 45359 ] New: Product Backlog April 2016 v2 [ 45360 ]
          Issue Type Original: Problem statement [ 10400 ] New: Story [ 10001 ]
          Status Original: Draft [ 10706 ] New: To Do [ 10003 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Assignee New: Gus Reiber [ deactivated user ]
          James Dumay made changes -
          Sprint New: 1.0-m8 [ 46 ]
          James Dumay made changes -
          Rank New: Ranked higher

          James Dumay added a comment -

          Explore two options:

          1. Similar to the "Changes" artboard in the Experiments when filtering by a specific branch
          2. Tests tab on Pipeline Result shows all changes in a failure series (grouped similar to the Branches tab work done previously)

          James Dumay added a comment - Explore two options: Similar to the "Changes" artboard in the Experiments when filtering by a specific branch Tests tab on Pipeline Result shows all changes in a failure series (grouped similar to the Branches tab work done previously)

          gus reiber added a comment -

          Nokia accomplished this ends by making the stage circles a little bigger and putting the last successful or first failing build number in the middle of the circle instead of an X or checkmark. The color was the only indicator of failure. In that way, the 2D pipeline view could also capture a sense of a dimension in time.

          gus reiber added a comment - Nokia accomplished this ends by making the stage circles a little bigger and putting the last successful or first failing build number in the middle of the circle instead of an X or checkmark. The color was the only indicator of failure. In that way, the 2D pipeline view could also capture a sense of a dimension in time.
          gus reiber made changes -
          Attachment New: Failing result.png [ 17417 ]
          gus reiber made changes -
          Attachment New: stage status.png [ 17418 ]

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: