[JIRA] (JENKINS-40871) UI support for milestone and lock
Title: Message Title Alejandro del Castillo commented on JENKINS-40871 Re: UI support for milestone and lock I ended up re-submitting the reference PR, which just got merged [1], which means that the work on this feature request should be unblocked. [1] https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/15 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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 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/
