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

When the run fails with tests or another analysis then it should be more obvious


    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None
    • tasman, frank, christmas


      When I upload a PR to GitHub and Jenkins responds with something bad and I click on details;
      In the traditional UI I get to the build page where I with a quick glance can most of the time directly see what is wrong, wether it's a test case that has failed or a checkstyle or findbugs violation etc.
      With BO I first get a blank page that load a bunch of stuff, compared to the traditional UI it takes forever, and during that load time I would have already found the culprit. And then I get a page that from my perspective shows me nothing except for a yellow color indicating an unstable build, but I sort of already knew that. And then I need to click around to find out what is wrong. While in the traditional build page I only need to click something to find out the details of why a particular thing is wrong.

      Possible solution

      • When we detect that tests that have failed (or another analysis that is the cause of a failed run) the log is not expanded and the "Issues detected" panel appears at the top of the screen.
      • Developer can click on the summary information in the issues detect and jump into analysis

            brody Brody Maclean
            jamesdumay James Dumay
            0 Vote for this issue
            5 Start watching this issue