and thanks nrayapati for the sample pipeline, most helpful

michaelneale jamesdumay the "limit" of 100 we're running into is due to the default pagination applied to the "nodes" endpoint. I'm not sure how important it is that we handle nodes > 100 in an elegant fashion. We can fix this a few different ways on the UI:

1. Make sure that pipeline graph renders but only show first 100 nodes.
2. Bump the limit up to something higher like 500 or 1000 nodes.
3. Add some logic to the UI so it traverses the paginated data until there are no more pages left.

I was chatting with vivek about this and he had some thoughts about the performance implications on the backend of fetching this much data. I believe he'll post a comment with some thoughts below.

michaelneale jamesdumay I've hardened some of the UI code so it's resistant to when we fetch 100 nodes but there are actually more - it just renders the first 100 in the graph. It's probably good to have that in place regardless, I just wanted you guys to make the call as to how much further we should go to support the n > 100 use case.

Thanks cliffmeyers Agree with you, to maintain the passivity the first option would be to show first 100 when the actual number is more than the limit.

And also it would be awesome if we can bump the limit slightly, 100 seems little low for me, may be just to 150 or 200 as we have most of our pipelines has just little over 100 stages. Just my 1¢.

Added a link to WIP PR.

Pipeline graph will no longer error out but the render but limited to 100 nodes. sophistifunk is doing some more involved improvements to pipeline graph and if we raise the limit, that work will be done there. I'll try to post an update to this ticket if that happens as a FYI.

Thanks a bunch cliffmeyers, is there any date that we can expect this code to be released? Thanks again.  

nrayapati sorry for the much-delayed reply here... it will be available in Blue Ocean 1.3. That should ship hopefully in the next week or so, or you can grab the 1.3 beta off experimental Jenkins update center.

cliffmeyers No thats fine, Thanks for an update.

cliffmeyers I have updated the plugin to 1.3.0 yesterday and it was working correctly for the existing jobs, how ever it is still a problem for the new jobs, this time it is a slight different error Error rendering PipelineRunGraph: TypeError: Cannot read property 'id' of undefined. Appreciate your help. Thank you. 

Also attaching the screenshot which has the js stack-trace too.