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

Blue Ocean Editor cannot load a valid Jenkinsfile on a Blue Ocean-created project

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      CloudBees Jenkins Enterprise 2.89.3.4-rolling with Blue Ocean 1.3.5
    • Similar Issues:

      Description

      During a training on Blue Ocean, one of our instance faced a weird error.

      After sucessfully building a pipeline (so valid Jenkinsfile), all tries to edit the pipeline using the Blue Ocean editor ends with the following error message: "Error loading Pipeline".

      See the attached "editor-error.png".

       

      The Jenkinsfile is valid and builds sucessfully. Its content is the following:

      pipeline {
        agent any
        stages {
          stage('Buzz Buzz') {
            steps {
              echo 'Bees Buzz!'
              echo 'Bees Buzz'
              echo 'new buzz'
              echo 'bees bees'
            }
          }
          stage('Bees Bees') {
            steps {
              echo 'Buzz, Bees, Buzz'
            }
          }
        }
      }
      

      The Multi Branch Pipeline project was in a weird state: the "Scan" button in the Classic UI was absent (see the screenshots "jenkins-homepage.png" and "mb-job-page.png"), while the default user is administrator and has all rights.

      This "Pipeline" had been created using the Blue Ocean "New Pipeline Wizard", on a Git Repository, using SSH.

      No configurations shifts looked like to have been occured between this instance and the others (the user never left Blue Ocean and don't even know what is the "Manage" page).

      I've attached a CloudBees support bundle, the Jenkins Logs output might help (the data inside is not sensitive so you got everything).

        Attachments

          Activity

          Hide
          dduportal Damien Duportal added a comment -

          Deleting the Multi Branch job and creating it again with Blue Ocean solved the issue.

          Show
          dduportal Damien Duportal added a comment - Deleting the Multi Branch job and creating it again with Blue Ocean solved the issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              dduportal Damien Duportal
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: