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

Pipeline editor not working if Script Path is set

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I have created a pipeline from a GitHub repository. Inside this repository, there is a subfolder called jenkins with a Jenkinsfile inside, just like in the example app: https://github.com/jenkins-docs/creating-a-pipeline-in-blue-ocean. Blue Ocean prompted me to design a new pipeline. Instead, I went to the settings and set the Script Path manually to 'jenkins/Jenkinsfile':

      It does work as intended. The hooks are activated and the pipeline is run properly, but if I try to edit the pipeline using pipeline editor, it shows an empty pipeline. If I do implement a pipeline in the editor and save it, a Jenkinsfile is created in the root of my repository.

      It seems the pipeline editor is not getting the Jenkinsfile path from 'Script Path' setting

        Attachments

          Issue Links

            Activity

            Hide
            andrejesus André Jesus added a comment -

            Hi!

            Have the same issue, not on a different path, but just with a different name.

            Can't find a solution for this.

            Show
            andrejesus André Jesus added a comment - Hi! Have the same issue, not on a different path, but just with a different name. Can't find a solution for this.
            Hide
            ms3cat Sam Zhao added a comment -

            Have the same problem. Only can build with a different Jankinsfile name. Can't modify pipeline by pipeline-editor.

            Show
            ms3cat Sam Zhao added a comment - Have the same problem. Only can build with a different Jankinsfile name. Can't modify pipeline by pipeline-editor.
            Hide
            antticgi Antti Turpeinen added a comment -

            I also have the same problem. We have multiple projects inside one git repository and we would like to use multiple Jenkinsfile. It would be great if we could use git sparse checkout and set Jenkinsfile inside those "sparsed" folders. At least the editor should be able to use the correct Jenkinsfile. 

            Show
            antticgi Antti Turpeinen added a comment - I also have the same problem. We have multiple projects inside one git repository and we would like to use multiple Jenkinsfile. It would be great if we could use git sparse checkout and set Jenkinsfile inside those "sparsed" folders. At least the editor should be able to use the correct Jenkinsfile. 
            Hide
            stelminator Christopher Stelma added a comment -

            I couldn't find any reference to the path in the /blue/rest/ api responses, which makes some sense because the objects on that API all seem to be from the perspective of the pipeline, not from the job that defines the pipeline.  i.e. I'm not sure where the path would go, maybe on the pipeline object, maybe on the scm object below that, but neither feels quite right.  However, since this is the api used to fill the editor, it really should go somewhere.

            Show
            stelminator Christopher Stelma added a comment - I couldn't find any reference to the path in the /blue/rest/ api responses, which makes some sense because the objects on that API all seem to be from the perspective of the pipeline, not from the job that defines the pipeline.  i.e. I'm not sure where the path would go, maybe on the pipeline object, maybe on the scm object below that, but neither feels quite right.  However, since this is the api used to fill the editor, it really should go somewhere.

              People

              • Assignee:
                lanwen Kirill Merkushev
                Reporter:
                vitor Vitor Durante
              • Votes:
                3 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: