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

Annotated block/stage status

    XMLWordPrintable

Details

    • Pipeline - July/August

    Description

      This ticket is closed – please read carefully

      Hi everyone,

      I am aware that this ticket is valued by many people. However, on review there are too many disparate use cases and problems attached to this issue that are already described elsewhere.

      This issue means too many things for too many people and makes it unsatisfiable with a single change. The appropriate action here is to close this ticket and ask watchers to watch and vote for a specific ticket that will solve their problem.

      If you are interested in these problems, please watch and vote for the following:

      • JENKINS-39203 - The entire pipeline gets marked as unstable rather than the stage or parallel where the unstable status was set.
      • JENKINS-45579 - Capability to mark a stage as "failed" with message and have the pipeline continue executing.
      • JENKINS-43995 - Infrastructure to allow any step to have its own distinct status. This enables the tickets listed above.
      • JENKINS-46170 - Add notes to stages and parallels

      I may have missed a few use cases. If that is the case:

      • Search JIRA for an issue matching your use case. If you find one, link it in the comments and I will update the ticket. Be sure to leave a comment on the linked ticket describing the problem you are trying to solve and then your desired solution to the problem.
      • If you cannot find an existing issue, raise a new one and comment here. Leave a comment on your new ticket describing problem you are trying to solve and then your desired solution to the problem.

      Thanks,
      James Dumay

      Original request
      It is often useful to provide more information up-front than a simple red or green "this step passed" or "this step failed". Our current in-house CI software has a "summary" field in its "Running Steps" equivalent, which can be filled with other info when a step finishes. For example, we have a step "upload-to-storage" which can optionally replace a "/latest/" symlink to the output it just uploaded. Either replacing or not replacing the symlink is correct, so we populate our "summary" field with the decision taken.

      I've attached an example from our current CI system - note that by allowing a step to populate its own summary, it means all pertinent information is available immediately to developers, on one page, rather than needing to always click through to log output for high-level information.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39203 All stages show up as UNSTABLE when only one stage should

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42130 Set status for Stages

          • Major - Major loss of function.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-35128 Ability to add additional information to stages

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-37851 Mark stages failed without aborting the pipeline

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-36087 Set stage result manually

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-26523 Allow yellow "unstable" state from a step

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-27395 distinguish test reports filed from different parts of workflow

          • Major - Major loss of function.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26107 Allow stage to operate as a labelled block

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29188 api URL for REST API is not available for flowGraphTable

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-34212 Visualization shows stage failed when an exception is caught

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-35453 Allow disabling the default commit status notifier

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          links to

          Web Link CloudBees Internal UX-578

          Web Link CloudBees Internal UX-643

          Web Link Design doc PR

          Web Link workflow-api-plugin#24

          Activity

            Ascending order - Click to sort in descending order
            View 39 older comments
            jamesdumay James Dumay added a comment -

            macdrega you are looking for JENKINS-38442 but its unlikely to be implemented at this time (we can't find a sane way to visualise it). Would you mind drawing a picture of your ideal visualisation and a mock Jenkinsfile, to help us figure out what you want? (attach and comment to JENKINS-38442)

            jamesdumay James Dumay added a comment - macdrega you are looking for JENKINS-38442 but its unlikely to be implemented at this time (we can't find a sane way to visualise it). Would you mind drawing a picture of your ideal visualisation and a mock Jenkinsfile, to help us figure out what you want? (attach and comment to JENKINS-38442 )
            macdrega Joerg Schwaerzler added a comment -

            Thanks for the quick answer - found that one already.

            I totally understand that nested stages are hard to visualize. I only need a small part of it: The only thing I need is just stages inside parallel blocks - without nesting one stage inside another stage, something like:

            That should be easy to visualize.

            Probably I'll create a new ticket hoping that it won't be closed in favor of  JENKINS-38442.

            macdrega Joerg Schwaerzler added a comment - Thanks for the quick answer - found that one already. I totally understand that nested stages are hard to visualize. I only need a small part of it: The only thing I need is just stages inside parallel blocks - without nesting one stage inside another stage, something like: That should be easy to visualize. Probably I'll create a new ticket hoping that it won't be closed in favor of   JENKINS-38442 .
            jamesdumay James Dumay added a comment -

            Mind posting this on the other ticket so that it's captured in the right place?

            jamesdumay James Dumay added a comment - Mind posting this on the other ticket so that it's captured in the right place?
            macdrega Joerg Schwaerzler added a comment -

            Sorry my fault . Post is already done now.

            macdrega Joerg Schwaerzler added a comment - Sorry my fault . Post is already done now.
            jamesdumay James Dumay added a comment -

            Thanks

            jamesdumay James Dumay added a comment - Thanks

            People

              Unassigned Unassigned
              directhex Jo Shields
              Votes:
              115 Vote for this issue
              Watchers:
              167 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: