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

2.0: provide better workflow visualization out of the box

      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:

          [JENKINS-31154] 2.0: provide better workflow visualization out of the box

          batmat thanks for the advise. I could install the plug-in from it.

          Slawa Giterman added a comment - batmat thanks for the advise. I could install the plug-in from it.

          Sam Van Oort added a comment -

          Yes, it is available in an alpha state and the full release is coming shortly; we're dependent on a workflow release before this can go out fully (the alpha depends on a workflow beta). The final review and feature inclusions for that are being negotiated presently.

          Sam Van Oort added a comment - Yes, it is available in an alpha state and the full release is coming shortly; we're dependent on a workflow release before this can go out fully (the alpha depends on a workflow beta). The final review and feature inclusions for that are being negotiated presently.

          Sam Van Oort added a comment -

          The plugin is now available via the main update center, we are currently migrating issues/docs content over and bringing the Wiki into full compliance.

          Sam Van Oort added a comment - The plugin is now available via the main update center, we are currently migrating issues/docs content over and bringing the Wiki into full compliance.

          Sam Van Oort added a comment -

          I am going ahead and closing this out, since we appear to have the necessary steps done for pipeline stage view.

          Sam Van Oort added a comment - I am going ahead and closing this out, since we appear to have the necessary steps done for pipeline stage view.

          Sam Van Oort added a comment -

          I am going ahead and closing this out, since we appear to have the necessary steps done for pipeline stage view.

          Sam Van Oort added a comment - I am going ahead and closing this out, since we appear to have the necessary steps done for pipeline stage view.

          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?

          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?

          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?

          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.

          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

          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

          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.

          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.

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

              Created:
              Updated:
              Resolved: