[JIRA] (JENKINS-36240) Default repository permission are not considered

[patth...@gmail.com (JIRA)]

Title: Message Title

Patrick Thiel commented on JENKINS-36240   Re: Default repository permission are not considered 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.. Submit a PR with changes to a project's Jenkinsfile (add an echo or something) Open up a PR and scan the repository. Observe, In the scan log, your PR will look something like the following: Checking pull request #1817 (not from a trusted source) Job name: PR-1817 ‘Jenkinsfile’ found Met criteria Since it's not a trusted source, when building this pull request, Jenkins will revert to using the Jenkinsfile on the base branch.. The log in the Jenkins PR job will look like this: Loading trusted files from base branch dev at {commit} rather than {commit} Seems related to this issue. I can file another defect for this, but I wanted to check in here first. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.