Details

    • Sprint:
      Pipeline - July/August
    • Similar Issues:

      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

            Activity

            directhex Jo Shields created issue -
            jglick Jesse Glick made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-26107 [ JENKINS-26107 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-26523 [ JENKINS-26523 ]
            jglick Jesse Glick made changes -
            Issue Type Bug [ 1 ] New Feature [ 2 ]
            jglick Jesse Glick made changes -
            Summary Annotated block results Annotated block/stage status
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-27395 [ JENKINS-27395 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-29188 [ JENKINS-29188 ]
            directhex Jo Shields made changes -
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-34212 [ JENKINS-34212 ]
            jglick Jesse Glick made changes -
            Epic Link JENKINS-35400 [ 171193 ]
            jglick Jesse Glick made changes -
            Link This issue is duplicated by JENKINS-35128 [ JENKINS-35128 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-35453 [ JENKINS-35453 ]
            svanoort Sam Van Oort made changes -
            Component/s pipeline-stage-view-plugin [ 21139 ]
            svanoort Sam Van Oort made changes -
            Link This issue is duplicated by JENKINS-36087 [ JENKINS-36087 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 160592 ] JNJira + In-Review [ 180414 ]
            svanoort Sam Van Oort made changes -
            Component/s pipeline-stage-view-plugin [ 21139 ]
            abayer Andrew Bayer made changes -
            Component/s pipeline-general [ 21692 ]
            abayer Andrew Bayer made changes -
            Component/s workflow-plugin [ 18820 ]
            jglick Jesse Glick made changes -
            Component/s pipeline-stage-step-plugin [ 21709 ]
            Component/s pipeline [ 21692 ]
            nitek Claus Näveke made changes -
            Link This issue is duplicated by JENKINS-37851 [ JENKINS-37851 ]
            svanoort Sam Van Oort made changes -
            Labels pipeline
            michaelneale Michael Neale made changes -
            Link This issue is duplicated by JENKINS-39203 [ JENKINS-39203 ]
            jamesdumay James Dumay made changes -
            Labels pipeline blueocean pipeline
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-39203 [ JENKINS-39203 ]
            jamesdumay James Dumay made changes -
            Link This issue blocks JENKINS-39203 [ JENKINS-39203 ]
            jamesdumay James Dumay made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            svanoort Sam Van Oort made changes -
            Status In Review [ 10005 ] In Progress [ 3 ]
            svanoort Sam Van Oort made changes -
            Assignee Jesse Glick [ jglick ] Sam Van Oort [ svanoort ]
            recampbell Ryan Campbell made changes -
            Remote Link This issue links to "workflow-api-plugin#24 (Web Link)" [ 15088 ]
            abayer Andrew Bayer made changes -
            Link This issue relates to JENKINS-43995 [ JENKINS-43995 ]
            svanoort Sam Van Oort made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            jglick Jesse Glick made changes -
            Link This issue is duplicated by JENKINS-42130 [ JENKINS-42130 ]
            abayer Andrew Bayer made changes -
            Remote Link This issue links to "Design doc PR (Web Link)" [ 16964 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.5 [ 371 ]
            jamesdumay James Dumay made changes -
            Assignee Sam Van Oort [ svanoort ] Andrew Bayer [ abayer ]
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35400 [ 171193 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] Open [ 1 ]
            jamesdumay James Dumay made changes -
            Assignee Andrew Bayer [ abayer ] James Dumay [ jamesdumay ]
            jamesdumay James Dumay made changes -
            Status Open [ 1 ] Closed [ 6 ]
            Resolution Incomplete [ 4 ]
            jamesdumay James Dumay made changes -
            Description 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.
            {panel:title=This ticket is closed – please read carefully|titleBGColor=grey|titleColor=white}
            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.

            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
            {panel}

            *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.
            macdrega Joerg Schwaerzler made changes -
            Attachment image-2017-08-14-10-27-14-670.png [ 39256 ]
            macdrega Joerg Schwaerzler made changes -
            Attachment image-2017-08-14-10-27-57-223.png [ 39257 ]
            jamesdumay James Dumay made changes -
            Description {panel:title=This ticket is closed – please read carefully|titleBGColor=grey|titleColor=white}
            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.

            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
            {panel}

            *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.
            {panel:title=This ticket is closed – please read carefully|titleBGColor=grey|titleColor=white}
            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
            {panel}

            *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.
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal UX-643 (Web Link)" [ 18188 ]
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal UX-578 (Web Link)" [ 18215 ]
            svanoort Sam Van Oort made changes -
            Resolution Incomplete [ 4 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            Assignee James Dumay [ jamesdumay ]
            svanoort Sam Van Oort made changes -
            Status Reopened [ 4 ] Closed [ 6 ]
            Resolution Incomplete [ 4 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                directhex Jo Shields
              • Votes:
                115 Vote for this issue
                Watchers:
                165 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: