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

2.0: provide better workflow visualization out of the box

    XMLWordPrintable

Details

    Description

      To make workflow more compelling, Jenkins 2.0 should provide a better visualization of the workflow execution out of the box.

      CloudBees is proposing to contribute the workflow stage view plugin to jump start this, which uses stage steps to drive the visualization of workflow runs as they progress through the pipeline:

      Attachments

        Issue Links

          Activity

            withnale Paul R added a comment -

            I've noticed that the 'Retry' and 'Download' links don't appear by default. After looking at the code, there seems to be an extension mechanism for controlling this area of the UI.

            We're currently using BuildPipeline steps and use the Restart functionality heavily. Is there any plans to make the Restart logic available with the StageView?

            withnale Paul R added a comment - I've noticed that the 'Retry' and 'Download' links don't appear by default. After looking at the code, there seems to be an extension mechanism for controlling this area of the UI. We're currently using BuildPipeline steps and use the Restart functionality heavily. Is there any plans to make the Restart logic available with the StageView?
            jzila John Zila added a comment - - edited

            The workflow graph is still overly verbose: Allocate node : Start is always followed by Allocate node : Body : Start, likewise with the step output for dir, timestamps, timeout, ws, withEnv, withRegistry, retry, wrap.

            This leads to unnecessarily deep trees and makes it difficult to parse. Can we collapse those nodes in the workflow graph to 1 deep instead of 2?

            jzila John Zila added a comment - - edited The workflow graph is still overly verbose: Allocate node : Start is always followed by Allocate node : Body : Start , likewise with the step output for dir , timestamps , timeout , ws , withEnv , withRegistry , retry , wrap . This leads to unnecessarily deep trees and makes it difficult to parse. Can we collapse those nodes in the workflow graph to 1 deep instead of 2?

            4c00h unfortunately I'm afraid the Retry feature is exclusive to Cloudbees' Jenkins Enterprise. I'm also currently using Build Pipeline Plugin and I really miss the Retry feature. I hope Cloudbees decides to make this feature free/open source.

            dserodio Daniel Serodio added a comment - 4c00h unfortunately I'm afraid the Retry feature is exclusive to Cloudbees' Jenkins Enterprise. I'm also currently using Build Pipeline Plugin and I really miss the Retry feature. I hope Cloudbees decides to make this feature free/open source.

            While we're already off-topic, in a closed ticket…

            jzila: You'd have to open a new ticket for that.
            dserodio: Or hope that Naginator (which works pretty good for retrying Freestyle builds) gets Pipeline support: JENKINS-37076

            orrc Christopher Orr added a comment - While we're already off-topic, in a closed ticket… jzila : You'd have to open a new ticket for that. dserodio : Or hope that Naginator (which works pretty good for retrying Freestyle builds) gets Pipeline support: JENKINS-37076
            jglick Jesse Glick added a comment -

            The workflow graph is still overly verbose

            Changes in this area planned anyway.

            the Retry feature is exclusive to Cloudbees' Jenkins Enterprise

            The feature name you are probably referring to is checkpoints. Core (OSS) Pipeline supports a Retry feature, which is quite different.

            jglick Jesse Glick added a comment - The workflow graph is still overly verbose Changes in this area planned anyway. the Retry feature is exclusive to Cloudbees' Jenkins Enterprise The feature name you are probably referring to is checkpoints. Core (OSS) Pipeline supports a Retry feature, which is quite different.

            People

              svanoort Sam Van Oort
              kohsuke Kohsuke Kawaguchi
              Votes:
              52 Vote for this issue
              Watchers:
              63 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: