Lack of a good pipeline visualization is the major blocker for Workflow adoption at our company. What's the expected timeframe for this contribution?

Same here, according to Kohsuke in the post below we should expect the visualization plugin to be freely available with Jenkins v2.0 on late Jan 2016.

https://groups.google.com/forum/#!topic/jenkinsci-dev/vbXK7JJekFw%5B1-25%5D

Until then we can be hard at work in perfecting our workflows . Any updates appreciated.

Yes same for me, I've been experiencing for some time with workflow pipelines and find it very powerfull but cannot migrate until it provides a good visualization status.
I tried to present it to other teams and their comments are always regarding a lack of visual representation.

Any updates are appreciated too.

+1

+1 Exactly the same situation here, workflow/pipelines would be very beneficial, both simplifying and enhancing some pipelines that we currently hack together using other plugins, but without visualization we cannot use it.
Role on Jan 2016

+1 Expect Jan 2016 too !

We see that workflow is pretty powerful to accomplish complex build and deployment scenarios, Looking forward for open source version of CloudBees plugin.

Any updates on this, Jan is almost at the end Looking forward to it being open source !!!

This is the repo which will contain the src from CloudBee:s implementenation: https://github.com/jenkinsci/pipeline-stage-view-plugin

The GitHub repo now contains the source code: https://github.com/jenkinsci/pipeline-stage-view-plugin

Thanks a lot for making this plug-in open source!

Is it possible now to install the plug-in with Jenkins ver. 1.642.1? I can see the plug-in in the Plug-Ins Wiki but not in the list of available plug-ins directly in Jenkins.

If it is not possible to install it from Jenkins Update site yet, is it possible to download the plug-in file to install it manually?

gitt apparently, the plugin has been released in alpha version. That means you should find in the experimental update center.

My 2 cents

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

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.

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.

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

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

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?

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.

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.