Gocd: Add value stream map including all pipelines

[dpsenner]

Currently the pipelines view is selected as primary view, but this does not give a good overview of the state of the pipelines. A value stream map based on the current configuration and the last build information would give a much better overview.

[srinivasupadhya]

I did not understand this clearly. Can you be more specific about "current configuration and the last build information"?

Note: You can have a look at issues already logged for vsm here & see if some of it is already logged.

[dpsenner]

Apologies, the title was misleading and I fixed that. To explain this further:

We have quite a lot of pipelines and stages and thus the pipelines view is totally crowded. To get an overview where in the pipeline stream something goes wrong one must either scroll around searching for the pipeline or by knowing whether one pipeline is in the upstream or downstream, he clicks on the latest label and gets a value stream map. A value stream map that displays all pipelines in a zoomable overview would improve that greatly as one immediatly sees if everything is green or not.

[amlozano]

+1 after some years...

The pipeline view doesn't give any information as soon as you get into a complicated setup with tens of pipelines.

In our case we have around 60 pipelines. Some of those pipelines are triggered automatically, and others are triggered manually .

In the current pipeline view you can only see the last execution status, but you don't know if a given pipeline was triggered for a given execution of a dependant pipeline. Example (all names represent pipelines):

Build => Integration Test => Deploy to Development -> Deploy to Production

=> represents automatic trigger, -> represents manual trigger

In the pipeline view, we will always see every status in green, with different information, and dates. But Deploy to Production could be not triggered for the last build, which is something that you can only see if you go to the VSM view.

Another thing that would be useful also to have in that view is the option to manually trigger any pipeline (https://github.com/gocd/gocd/issues/2163). From the VSM there is no option to trigger, so in our case we have to check that the last step was not triggered, go back to the pipeline view, look again for the pipeline name called Deploy to Production, and click on it.

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.