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

pipeline-editor always commit to default jenkinsfile

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

        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

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: