-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
We have larger job chains with more than 50 jobs in one build flow.
It is great to have a way to visualize these but having the huge graph on the job page is not really good.
Also for pipelines the build flow graph is placed above the stage view so you will have to scroll down to the stage view if your job chain is too long.
Maybe this can be solved with a configurable limit of displayable nodes? And then give the possibility to extend the graph or just open it in a new window.
[JENKINS-58823] Improve visualization for large job chains
I just found a example with probably several hundred of jobs within the chain.
Joschua Grube
added a comment - - edited I just found a example with probably several hundred of jobs within the chain.
Ok. That's an impressive graph 
I think a OKish way forward would be to identify when a huge graph like that is about to be painted and in those cases replace the graph with a link to the "<build url>/yabv" page (which is already implemented, you can try it yourself).
We could even make it configurable, like allowing the Jenkins admin to specify a threshold.
Does that sounds like decent enough compromise?
Joschua Grube
added a comment - Yea this sounds like a good solution.
It would be cool if we had something like a "preview" which just shows a few jobs and then the link to the full graph. But it might be difficult to implement.
Joschua Grube
added a comment - Yea this sounds like a good solution.
It would be cool if we had something like a "preview" which just shows a few jobs and then the link to the full graph. But it might be difficult to implement. Hmm.. I'll thinker a bit with the preview idea and we'll see if I can come up with something decent. I just want to be sure that I clearly can convey to the end user that only part of the Build Flow is currently shown.
this request also includes the option to move the graph BELOW the pipeline output - my team votes for this option as well
and if you are considering adding limits to upstream, downstream, please include siblings limits as well.
Thanks for the report, Joschua.
50 jobs does not sound like that much. Could you post a screenshot or two, so I can get a more clear picture of the size and placement of the Build Flow?
/Gustaf