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

Skipped tests should not use "unstable" coloring

    XMLWordPrintable

Details

    • 1.0, Blue Ocean - 1.1-beta2

    Description

      Scope

      • Change skipped tests to use the "not built" style and status indicator instead of the yellow "unstable" style and status indicator

      Original request
      In an unstable build, there can be

      • failed tests
      • skipped tests

      The skipped tests are the same color and icon as the overall build (orange and ! ) while the tests that actually made the build unstable are red and x. This makes no sense, as it implies a relationship between build status and skipped tests that's just not there.

      Attachments

        Activity

          jamesdumay James Dumay added a comment -

          Will be released in Blue Ocean 1.1

          jamesdumay James Dumay added a comment - Will be released in Blue Ocean 1.1
          jamesdumay James Dumay added a comment -

          danielbeck it now looks like this

          jamesdumay James Dumay added a comment - danielbeck it now looks like this
          brody Brody Maclean added a comment -

          jamesdumay skipped ≠ unstable so it doesn't make sense to have the same status or colour.
          grey currently is used for aborted... which does have some relation to skipped so that could work.

          brody Brody Maclean added a comment - jamesdumay skipped ≠ unstable so it doesn't make sense to have the same status or colour. grey currently is used for aborted... which does have some relation to skipped so that could work.
          danielbeck Daniel Beck added a comment -

          Yes. It was actually confusing to me trying to understand the icons here – the tests with the same icon as "the entire build" were basically irrelevant. Something grey would be better here, and perhaps even consider changing the failed "red x" icon to "orange !" to match the build step.

          danielbeck Daniel Beck added a comment - Yes. It was actually confusing to me trying to understand the icons here – the tests with the same icon as "the entire build" were basically irrelevant. Something grey would be better here, and perhaps even consider changing the failed "red x" icon to "orange !" to match the build step.
          jamesdumay James Dumay added a comment -

          danielbeck oh are you saying "skipped" tests shouldn't have the same state as "unstable"? I agree. Since skipped tests are not built, WDYT about using the "not built" status here brody?

          jamesdumay James Dumay added a comment - danielbeck oh are you saying "skipped" tests shouldn't have the same state as "unstable"? I agree. Since skipped tests are not built, WDYT about using the "not built" status here brody ?
          danielbeck Daniel Beck added a comment -

          jamesdumay Please see the screenshot for what this is about.

          danielbeck Daniel Beck added a comment - jamesdumay Please see the screenshot for what this is about.
          jamesdumay James Dumay added a comment -

          You are right - it does not make sense. Pipeline actually sets every node as unstable and Blue Ocean just reports on what pipeline tells it. I do have internal commitment from CloudBees OSS team that they will fix it this year for me. Need to narrow down when because it annoys me a lot.

          jamesdumay James Dumay added a comment - You are right - it does not make sense. Pipeline actually sets every node as unstable and Blue Ocean just reports on what pipeline tells it. I do have internal commitment from CloudBees OSS team that they will fix it this year for me. Need to narrow down when because it annoys me a lot.

          People

            jamesdumay James Dumay
            danielbeck Daniel Beck
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: