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 get that merged to master 2. Then checkout the new master, create a new branch and change the dummy version of the file and then create the PR 3. And then create the multibranch pipeline script The side effect of this is that the scan repository checks out the current HEAD and then merges that change to all currently opened PRs. This means that the new script, that I only want to test on one PR branch, the dummy version on HEAD gets applied to all open PRs regardless of the file existing or not existing there. This seems wrong to me. So the answer to the original question is "yes you can set Script Path to anything as long as it currently exists on the repo's master". Kind regards, Ian -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8f41a340-5f2e-4ec4-95a4-a564fbb7a803%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
