[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set
Title: Message Title Sam Zhao commented on JENKINS-50328 Re: Pipeline editor not working if Script Path is set Have the same problem. Only can build with a different Jankinsfile name. Can't modify pipeline by pipeline-editor. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51066) pipeline-editor always commit to default jenkinsfile
Title: Message Title Sam Zhao stopped work on JENKINS-51066 Change By: Sam Zhao Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51066) pipeline-editor always commit to default jenkinsfile
Title: Message Title Sam Zhao started work on JENKINS-51066 Change By: Sam Zhao Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51066) pipeline-editor always commit to default jenkinsfile
Title: Message Title Sam Zhao created an issue Jenkins / JENKINS-51066 pipeline-editor always commit to default jenkinsfile Issue Type: Bug Assignee: Unassigned Attachments: screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png Components: blueocean-pipeline-editor-plugin Created: 2018-05-02 10:25 Environment: Jenkins ver. 2.73.3 BlueOcean 1.5.0 - Core 2.73.3 Labels: jenkins blueocean-imported Priority: Major Reporter: Sam Zhao 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:///blue/organizations/jenkins/pipeline-editor// 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.
