[Feature Request] VSM for whole config

[srinivas upadhya]

Quiet a few people have asked for this feature. Wanted to show some spike that i have written (attached screenshot).

Purpose:

To provide dependency view of whole of config.

Details:

The pipeline name is link to pipeline edit: '/go/admin/pipelines/<pipeline-name>/general'

The stage bar is link to stage edit: '/go/admin/pipelines/<pipeline-name>/stages/<stage-name>/settings'

The dependency arrow could be link to: '/go/admin/pipelines/<pipeline-name>/materials'?

Features (that can be built on top of this):

1. Addition & deletion of dependency for a pipeline.
2. Clone VSM feature where user can select a set of pipeline (along with dependencies) and clone at once.

Thoughts?

[Maulik Suchak]

+1 for this. I like the idea of bringing config/admin part into the VSM.

Few suggestions/points.

- IMO, better we extend/enhance existing VSM to accommodate what you've mentioned here, thoughts?

- Moreover, if we decide to keep this as separate page (not with VSM), I'd say we can rename "Config XML" tab to just say "Config" and have 2 sub-tabs under that having "with XML" and "with VSM"? 

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Maulik Suchak

www.maulik.co

[Jaume Sancho]

Agree that this would be an incredible addition to Go.

Some more suggestions:
- The "Global VSM" view could be associated to the pipeline groups.

- I also think that this could probably fit into the main dashboard.
Just like there is "personalize" dropdown for group/pipeline filtering, the view mode could be adjusted with a switch between "grid view"/"VSM view"

In my current config I have 20+ pipelines and it's always bit overwhelming to the new users that I am introducing to the platform.

thanks,

Jaume

[srinivas upadhya]

VSM for config grouped by "pipeline group" could be tricky since the dependency is not restricted by groups.

VSM for dashboard is also being asked by many. But the main problem is the difficulty in showing the "correct information". Currently the dashboard shows all active instances of a pipeline. So in a dependency graph like:

Git +-> A -+-> C

    |-> B -|

and if C has 2 instances running, it would be difficult to show the correct instances of A & B that are responsible for different instances of C running on same graph.

[Marius Ciotlos]

Ok, I seem to have misread this topic! The idea is purely AWESOME. 

I totally agree we should have VSM on top of the config.xml showing all dependency graph, however this is not usable with super large configurations. I agree we should have this view grouped by, or filtered by Pipeline Groups. I agree that downstream dependencies can go out of the current Pipeline Group, but this is easily fixable by using different colours. 

Let's take 3 use cases:

1. You have all pipelines within a Group with no upstream or downstream dependencies outside:

> You click on a group VSM link (see my proposed screenshot) and you see the VSM view for that group. 

2. You have upstream pipelines that are in different Pipeline group:

> You view the whole VM for your group like in point 1. and with different colour all the upstream dependent pipelines that would get your material to the pipelines in your group (skipping any downstream pipelines for those that are not part of your group or contribute to the dependencies, just like you do now for the current VSM when clicking on the label)

3. You have downstream pipelines that are in different group:

> You click on the icon for current group, or whatever method is used to filter it out, and you get the view as in point 1 and where you have downstream pipelines, you show those in different colour. I guess there is also the point that you have (group1) -> (group 2) -> (group 1) dependency, but that would still work. I just think there are fewer use cases. 

I'll post below my proposed views

[srinivas upadhya]

May be showing a dropdown with list of groups & rendering pipelines in the selected group as dependency could be done. This should reduce the performance concerns for large configs as well.

May be there could be an option to render the whole of config as well.

And rendering upstream & downstream of a pipeline. Like how we do current VSM.

I really like the VSM icon on group & pipeline.