Re: Multibranch pipeline script path doesn't work with anything other then Jenkinsfile

2017-09-01 Thread Stephen Connolly
Likely your PRs are not "trusted". If the PR is "trusted" then the PR's Jenkinsfile can be used. Check what trust strategy you configured when defining the source On 1 September 2017 at 07:13, 'Ian Smith' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Turns out that in the

Re: Multibranch pipeline script path doesn't work with anything other then Jenkinsfile

2017-09-01 Thread 'Ian Smith' via Jenkins Users
Turns out that in the multibranch scan repository it only checks if the file in the Script Path exists on the HEAD. So if I want to check that a new script, that is currently being developed, works with Jenkins then I need to 1. Create a PR that creates a dummy version of the file and then

Multibranch pipeline script path doesn't work with anything other then Jenkinsfile

2017-08-31 Thread 'Ian Smith' via Jenkins Users
Hi, I'm trying to run two distinct pipelines from one repo. So currently I have an existing multibranch pipeline that uses a Jenkinsfile at the top of the repo. This is triggered on both an update to a PR branch and when a merge to the HEAD happens on github. I want a second pipeline to only