When one opens the value stream map it is not refreshed from time to time and one has to reload the page to see the pipeline progress.
Yes its currently not present since VSM data could be very heavy (in terms of DB calls & visual optimization for graph data) & an auto-refresh could worsen this. If people are fine with the performance bit it shouldn't be difficult to put one.
Probably we could move visual optimization part to client (browser/js) end to make it better?
Changing the graph sure is heavy, but having open one stream map it will not change the graph unless the configuration is changed in the meanwhile. That surely is a limitation, but a corner case that can be addressed otherwise. Based on which pipeline/stage is executing the client could poll just a subset of stages/pipelines which will be invoked after that. Basically the client would start to follow the pipeline stream.
There's another issue coming along with the missing refresh: if one refreshes the view by reloading the page it will loose the position one has navigated to. With a large enough value stream map this is awfully painful.
This is a big roadblock for us moving from Jenkins to GoCD.
Our delivery pipeline is currently implemented as jenkins jobs in which the test phases are run concurrently and the jenkins pipeline view plugin provides our default view (no-one even looks at the main view showing a bunch of jobs. we;re only interested in seeing them in pipeline form).
The VSM is the equivalent view since that kind of concurrent execution is achieved in GoCD via seperate pipelines (rather than stages or jobs which would be the GoCD equiv to a jenkins job).
But without the status updating in real-time (or a decently small poll period) the VSM is useless to us and the "non-pipelined" (to us) default view is worse.
I am surprised that there is so little interest since 2014 for improvement in this area of the VSM.
Am I missing something?
We've moved from GoCD to gitlab / gitlab-runner.. (the community edition)