I have attached a HAR file from that page load. I'm seeing a few 500 errors, but looks to be from the favourites api, not sure if it has any effect on the pipeline graph.

noodlesnz re: favorites - you might need to check that all your plugin versions are up to date.

All up to date, running Jenkins 2.29 as well

noodlesnz did you perform a restart after updating?

noodlesnz I found the 500 error JENKINS-39600

Thanks James, I'll look out for the plugin update for favourites.

I restarted after updating and just restarted now, but still no graph.

noodlesnz can you hit the URL at http://jenkins.woolshed.com:8080/blue/rest/organizations/jenkins/pipelines/questioncom/branches/master/runs/6/nodes/ and share the content with me? That contains the data that the graph uses to draw your pipeline

It shows:

[]

noodlesnz ahh thanks. That would indicate that there are no "flow nodes" that describe the flow of the graph.

noodlesnz could you try executing the following Pipeline using the "Pipeline Job" type? Run it twice, taking screenshots of both results.

  node {
    stage ('First') {
      sh 'ping -c 10 apple.com'
    }
    stage ('Second') {
      sh 'ping -c 10 apple.com'
    }
  }

noodlesnz looks like Apple is slow to ping today so ping exits with code 2.

I updated the pipeline to ping localhost instead - try with this version

  node {
    stage ('First') {
      sh 'ping -c 10 localhost'
    }
    stage ('Second') {
      sh 'ping -c 10 localhost'
    }
  }

Thanks, I have attached the two screen shots

noodlesnz Looked in to you HAR, GEThttp://jenkins.woolshed.com:8080/blue/rest/organizations/jenkins/pipelines/questioncom/branches/master/runs/6/nodes/ HTTP/1.1 indeed is giving empty nodes.

Can you check if pipeline-model-definition plugin is installed and what version it is?

This seems to be resolved with Jenkins 2.30 and Favorites plugin 2.0.2. I'm not sure how/why, but the graph is showing for builds now.

noodlesnz thats great news. What version of Jenkins were you running prior?

I was running 2.29, I think 2.30 was released today

Ill try with that exact version now.

Hmm, its weird that I can't even get 2.29 to work locally. When I install plugins, one or two fail to load and then the instance is busted.

Looks like 2.29 had a major regression where stages wouldn't be displayed (JENKINS-39555) which has been fixed in 2.30.

noodlesnz I highly recommend using the Jenkins LTS version as there is a lot of volatility with the weekly releases you are using.