[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Sprint: post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay commented on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization Thanks Alejandro del Castillo this certainly gives us more to work with. Thanks for being quick to reply! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title Alejandro del Castillo commented on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization I think there is value in keeping the pipelines that were aborted. From a user's point of view, his submission creates a pipeline instance and that's all he cares. The tricky part is how to convey visually that a pipeline was aborted/replaced by another one. A link (like the one you proposed) works, but maybe it's possible to show that information on the pipeline visual itself instead of a link. Maybe we can show the running stages on the pipeline view of the aborted pipeline with a different color? Not sure if that "fits" with blue ocean paradigmsjust a suggestion to consider since I am not a UX person. Thanks for taking the time to look at this issue! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40871
Running Pipeline Status with Milestone/Locks Needs Better visualization
Change By:
James Dumay
It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point.Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after.Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way?[1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/*Technical notes*{{CancelledCause}} contains the data needed to find out what run replaced one that was canceled. {{CancelledCause}} is set on the Runs {{InterruptedBuildAction}}.This [pull request|https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/7] should allow the {{CancelledCause}} to serialize all the data we need to do the work here. *Design notes*The run that does succeed should roll up all the changesets of the aborted runs that came before it since the last non-aborted run. Perhaps we should be doing this for whole series of successful runs?
Add Comment
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay edited a comment on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization [~adelcast] do you ever want to see the Pipelines that were aborted because of milestone/lock when you view the run history? Should we be hiding them? !activity.png|thumbnail! What if we had a message on the run screen that told you that it had been replaced and allowed you to click through ? !run.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Attachment: JENKINS-40871 #25 2017-01-08 13-35-49.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay edited a comment on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization [~adelcast] do you ever want to see the Pipelines that were aborted because of milestone/lock when you view the run history? Should we be hiding them? ! JENKINS-40871 2017-01-08 13-34-22 activity .png|thumbnail! What if we had a message on the run screen that told you that it had been replaced? ! JENKINS-40871 #25 2017-01-08 13-35-49 run .png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Attachment: activity.png Attachment: run.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Attachment: JENKINS-40871 2017-01-08 13-34-22.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay commented on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization Alejandro del Castillo do you ever want to see the Pipelines that were aborted because of milestone/lock when you view the run history? Should we be hiding them? ! JENKINS-40871 2017-01-08 13-34-22.png|thumbnail! What if we had a message on the run screen that told you that it had been replaced? ! JENKINS-40871 #25 2017-01-08 13-35-49.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay edited a comment on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization [~adelcast] do you ever want to see the Pipelines that were aborted because of milestone/lock when you view the run history? Should we be hiding them? ! JENKINS-40871 2017-01-08 13-34-22.png|thumbnail! What if we had a message on the run screen that told you that it had been replaced? ! JENKINS-40871 #25 2017-01-08 13-35-49.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Attachment: JENKINS-40871 #25 2017-01-08 13-35-49.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Attachment: JENKINS-40871 2017-01-08 13-34-22.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40871
Running Pipeline Status with Milestone/Locks Needs Better visualization
Change By:
James Dumay
It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point.Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after.Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way?[1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/*Technical notes*{{CancelledCause}} contains the data needed to find out what run replaced one that was canceled. {{CancelledCause}} is set on the Runs {{InterruptedBuildAction}}. This [pull request|https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/7] should allow the {{CancelledCause}} to serialize all the data we need to do the work here.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40871
Running Pipeline Status with Milestone/Locks Needs Better visualization
Change By:
James Dumay
It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point.Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after.Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way?[1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/ *Technical notes*{{CancelledCause}} contains the data needed to find out what run replaced one that was canceled. {{CancelledCause}} is set on the Runs {{InterruptedBuildAction}}.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay commented on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization Thanks for this improvement suggestion Alejandro del Castillo and certainly we should be making the experience here a bit cleaner for users of milestone and lock. I think we will need some more time to dive into this problem and Ill expect we will return to this after the Blue Ocean 1.0 at the end of March. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Change By: James Dumay Sprint: post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title Alejandro del Castillo created an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Issue Type: Improvement Assignee: Unassigned Attachments: batch_pipeline.jpg Components: blueocean-plugin Created: 2017/Jan/06 10:01 PM Priority: Major Reporter: Alejandro del Castillo It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point. Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after. Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way? [1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
