John Zila added a comment - 2017-01-19 22:15 +1. In my config this makes PR builds useless, because they're always building master.

Patrick Thiel added a comment - 2017-01-19 22:42 +1.. This is pretty much a blocker for us. We were right in the middle of migrating to using Jenkinsfiles and multibranch pipelines when we encountered this. Basically, if you don't already have a Jenkinsfile merged to the base branch (say your PR contains a WIP Jenkinsfile, like in our case), then Jenkins throws an error stating no Jenkinsfile found. It's only loading trusted files from the base branch which at this point doesn't contain a jenkins file, so nothing runs. Here are some steps to reproduce that i posted in another comment: Using a multibranch pipeline project with the latest SCM API 2.0 release, we have also noticed PR's from contributors getting flagged as untrusted sources.. Despite the PR author having admin privileges as a contributor and is the member of a Github team that also has Write permissions for the repository. To test this.. Build settings: [x] Build origin PRs (unmerged head) Submit a PR to origin base branch with changes to the Jenkinsfile (add an echo or something) Open up a PR and scan the repository. Observe, In the scan log, the source will appear untrusted Jenkins will checkout the base branch instead The base branch Jenkinsfile is executed The repository scan log looks like this: Checking pull request #1817 (not from a trusted source) Job name: PR-1817 ‘Jenkinsfile’ found Met criteria Jenkins PR job log: Loading trusted files from base branch dev at {commit} rather than {commit}

marc young added a comment - 2017-01-20 20:49 I have the same issue. Linking https://issues.jenkins-ci.org/browse/JENKINS-37931

Daniel Beck added a comment - 2017-01-23 12:03 This issue predated SCM API 2.0.