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

BuildPipelinePlugin - After upgrade to 2.121.1 the build pipeline view fails to load

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • build-pipeline-plugin
    • None
    • Docker (official jenkins/jenkins:2.121.1 image)
      build-pipeline-plugin: 1.5.8

      After upgrading to Jenkins 1.121.1 LTS the build-pipeline view fails with the following error in the logs:

      Jun 18, 2018 10:08:18 AM SEVERE au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView hasPermissionError in hasPermission:
      {{ java.lang.NullPointerException}}

       

      When I create the Jenkins master from scratch (no uodate from a previous version of Jenkins), the plugin works fine.

          [JENKINS-51997] BuildPipelinePlugin - After upgrade to 2.121.1 the build pipeline view fails to load

          This issue might have the same root cause as the two linked issues, but shows a different error message.

          Tobias Getrost added a comment - This issue might have the same root cause as the two linked issues, but shows a different error message.

          I attached the configuration of the view before the upgrade (BuildPipelineConfig_old.xml) and after setting up the server with Jenkins 2.121.1 LTS from scratch (BuildPipelineConfig_new.xml).

          The difference is that the "new" configuration contains 3 new elemens: rowHeaders, columnHeaders and buildCard.

          This build-pipeline-plugin was not updated in this upgrade.

          Tobias Getrost added a comment - I attached the configuration of the view before the upgrade ( BuildPipelineConfig_old.xml ) and after setting up the server with Jenkins 2.121.1 LTS from scratch ( BuildPipelineConfig_new.xml ). The difference is that the "new" configuration contains 3 new elemens: rowHeaders , columnHeaders and buildCard . This build-pipeline-plugin was not updated in this upgrade.

          Dan Alvizu added a comment -

          Sorry - this was lost. Can you confirm your plugin version? This was expected to be fixed in JENKINS-45137 in 1.5.8.

          Dan Alvizu added a comment - Sorry - this was lost. Can you confirm your plugin version? This was expected to be fixed in  JENKINS-45137 in 1.5.8.

          Hi dalvizu, we are using 1.5.8, Jenkins version 2.107.3

          Daniel Galassi added a comment - Hi dalvizu , we are using 1.5.8, Jenkins version 2.107.3

          Mark Waite added a comment -

          Works for me with Jenkins 2.426.2

          Mark Waite added a comment - Works for me with Jenkins 2.426.2

            Unassigned Unassigned
            getrostt Tobias Getrost
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: