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

      Problem

      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

          [JENKINS-39892] When the run fails with tests or another analysis then it should be more obvious

          James Dumay created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-35755 [ 171716 ]
          James Dumay made changes -
          Description Original: *Problem*
          {quote}
          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.
          {quote}
          New: *Problem*
          {quote}
          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.
          {quote}

          *Possible solution*
          * When we detect that tests (or another analysis) is the cause of the failure 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
          James Dumay made changes -
          Sprint New: tasman [ 136 ]
          James Dumay made changes -
          Rank New: Ranked higher

          Oleg Nenashev added a comment -

          If the test run marks the build unstable instead of Failed, it should be also visible. In https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/113/pipeline I get an unstable state, but all Pipeline steps are being shown as green. It complicates the analysis if you have multiple test result publishing steps

          Oleg Nenashev added a comment - If the test run marks the build unstable instead of Failed, it should be also visible. In https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/113/pipeline I get an unstable state, but all Pipeline steps are being shown as green. It complicates the analysis if you have multiple test result publishing steps

          James Dumay added a comment -

          oleg_nenashev if there are any failed tests we will show this summary

          James Dumay added a comment - oleg_nenashev if there are any failed tests we will show this summary
          James Dumay made changes -
          Description Original: *Problem*
          {quote}
          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.
          {quote}

          *Possible solution*
          * When we detect that tests (or another analysis) is the cause of the failure 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
          New: *Problem*
          {quote}
          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.
          {quote}

          *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

          Oleg Nenashev added a comment -

          jamesdumay But from what I see in Summary I won't be able to determine which test reporting step caused the failure. If I do the test parallelization across multiple machines, it will be complicated.

          Oleg Nenashev added a comment - jamesdumay But from what I see in Summary I won't be able to determine which test reporting step caused the failure. If I do the test parallelization across multiple machines, it will be complicated.

          James Dumay added a comment - - edited

          oleg_nenashev we can't do that until JENKINS-27395 is fixed. ping svanoort hrmpw

          James Dumay added a comment - - edited oleg_nenashev we can't do that until JENKINS-27395 is fixed. ping svanoort hrmpw

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

              Created:
              Updated: