Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
-
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
-
JENKINS-39203 All stages show up as UNSTABLE when only one stage should
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
JENKINS-36087 Set stage result manually
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
(6 is related to, 1 relates to, 4 links to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is related to |
| Link |
This issue is related to |
| Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
| Summary | Annotated block results | Annotated block/stage status |
| Link |
This issue is related to |
| Link |
This issue is related to |
| Attachment | Screenshot from 2016-04-05 14-30-24.png [ 32360 ] | |
| Attachment | Screenshot from 2016-04-05 14-28-42.png [ 32361 ] |
| Link |
This issue is related to |
| Epic Link | JENKINS-35400 [ 171193 ] |
| Link |
This issue is duplicated by |
| Link |
This issue is related to |
Sam Van Oort
made changes -
| Component/s | pipeline-stage-view-plugin [ 21139 ] |
Sam Van Oort
made changes -
| Link |
This issue is duplicated by |
| Workflow | JNJira [ 160592 ] | JNJira + In-Review [ 180414 ] |
Sam Van Oort
made changes -
| Component/s | pipeline-stage-view-plugin [ 21139 ] |
| Component/s | pipeline-general [ 21692 ] |
| Component/s | workflow-plugin [ 18820 ] |
| Component/s | pipeline-stage-step-plugin [ 21709 ] | |
| Component/s | pipeline [ 21692 ] |
Claus Näveke
made changes -
| Link |
This issue is duplicated by |
Sam Van Oort
made changes -
| Labels | pipeline |
| Link |
This issue is duplicated by |
| Labels | pipeline | blueocean pipeline |
| Link |
This issue is duplicated by |
| Link |
This issue blocks |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
Sam Van Oort
made changes -
| Status | In Review [ 10005 ] | In Progress [ 3 ] |
Sam Van Oort
made changes -
| Assignee | Jesse Glick [ jglick ] | Sam Van Oort [ svanoort ] |
Ryan Campbell
made changes -
| Remote Link | This issue links to "workflow-api-plugin#24 (Web Link)" [ 15088 ] |
| Link |
This issue relates to |
Sam Van Oort
made changes -
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Link |
This issue is duplicated by |
| Remote Link | This issue links to "Design doc PR (Web Link)" [ 16964 ] |
| Sprint | Blue Ocean 1.5 [ 371 ] |
| Assignee | Sam Van Oort [ svanoort ] | Andrew Bayer [ abayer ] |
| Epic Link | JENKINS-35400 [ 171193 ] |
| Status | In Progress [ 3 ] | Open [ 1 ] |
| Assignee | Andrew Bayer [ abayer ] | James Dumay [ jamesdumay ] |
| Resolution | Incomplete [ 4 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| 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: * * * 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. |
| Attachment | image-2017-08-14-10-27-14-670.png [ 39256 ] |
| Attachment | image-2017-08-14-10-27-57-223.png [ 39257 ] |
| 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: * * * 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-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. |
| Remote Link | This issue links to "CloudBees Internal UX-643 (Web Link)" [ 18188 ] |
| Remote Link | This issue links to "CloudBees Internal UX-578 (Web Link)" [ 18215 ] |
Sam Van Oort
made changes -
| Assignee | James Dumay [ jamesdumay ] | |
| Resolution | Incomplete [ 4 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
Sam Van Oort
made changes -
| Resolution | Incomplete [ 4 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Epic Link | JENKINS-35400 [ 171193 ] |