Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39599

Pipeline graph not rendering for a simple Pipeline

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • blueocean-plugin
    • None

      The following Pipeline

      #!groovy
      def ant(stage){
        sh "/usr/bin/ant $stage"
      }
      
      node {
        stage('Checkout') {
          checkout scm
        }
          
        stage('Build') {
          echo 'Something'
        }
      }
      

      Renders without stages

          [JENKINS-39599] Pipeline graph not rendering for a simple Pipeline

          That pipeline job results in a failure for some reason. Is this would you would expect?

          Nick Le Mouton added a comment - That pipeline job results in a failure for some reason. Is this would you would expect?

          James Dumay added a comment -

          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'
              }
            }
          

          James Dumay added a comment - 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

          Nick Le Mouton added a comment - Thanks, I have attached the two screen shots

          Vivek Pandey added a comment - - edited

          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?

          Vivek Pandey added a comment - - edited 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.

          Nick Le Mouton added a comment - 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.

          James Dumay added a comment -

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

          James Dumay added a comment - noodlesnz thats great news. What version of Jenkins were you running prior?

          I was running 2.29, I think 2.30 was released today

          Nick Le Mouton added a comment - I was running 2.29, I think 2.30 was released today

          James Dumay added a comment -

          Ill try with that exact version now.

          James Dumay added a comment - Ill try with that exact version now.

          James Dumay added a comment -

          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.

          James Dumay added a comment - 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.

          James Dumay added a comment - - edited

          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.

          James Dumay added a comment - - edited 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.

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: