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

pipeline-editor always commit to default jenkinsfile

      Hi,

      When we use more than one Jenkinsfile in different jobs, you can see screenshot 1, pipeline scans the right 'Jenkinsfile-prd' for example(screenshot2). And when execute the pipeline it also use the right 'Jenkinsfile-prd'(screenshot3).

      But when use http://<jenkins_url>/blue/organizations/jenkins/pipeline-editor/<jobname>/<branch> to edit pipeline, it always shows the default Jenkinsfile and only can commit to default Jenkinsfile.(screenshot4).

      It seems /blue/organizations/jenkins/pipeline-editor/ always read the default Jenkinsfile and ignored the Build Configuration--Script Path.

      The difference between 2 Jenkinsfiles are environment: env in this example.

        1. jenkinsBUG1.png
          jenkinsBUG1.png
          34 kB
        2. JenkinsBug2.png
          JenkinsBug2.png
          36 kB
        3. screenshot1.png
          screenshot1.png
          91 kB
        4. screenshot2.png
          screenshot2.png
          85 kB
        5. screenshot3.png
          screenshot3.png
          79 kB
        6. screenshot4.png
          screenshot4.png
          34 kB

          [JENKINS-51066] pipeline-editor always commit to default jenkinsfile

          Wang You added a comment -

          I have the same problem.
          And i found that it was EditorPage.jsx that did not specify the path parameter.

          ScmContentApi.js:

          EditorPage.jsx:

          Wang You added a comment - I have the same problem. And i found that it was EditorPage.jsx that did not specify the path parameter. ScmContentApi.js: EditorPage.jsx:

          I've got the same issue

          Nikolay Blindov added a comment - I've got the same issue

          Karl Shultz added a comment -

          This looks to be a more in-depth write up of the previously-existing JENKINS-50328, We should probably close one or the other of them.

          Karl Shultz added a comment - This looks to be a more in-depth write up of the previously-existing JENKINS-50328 , We should probably close one or the other of them.

          J P added a comment -

          Submitted PR with potential fix here: https://github.com/jenkinsci/blueocean-plugin/pull/2049

           

          J P added a comment - Submitted PR with potential fix here: https://github.com/jenkinsci/blueocean-plugin/pull/2049  

          J P added a comment -

          Fixed in BlueOcean 1.22.0

          J P added a comment - Fixed in BlueOcean 1.22.0

            jamesdumay James Dumay
            ms3cat Sam Zhao
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: