[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds

[email protected] (JIRA) Thu, 19 Jan 2017 10:07:46 -0800

Title: Message Title

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 write OR admin privileges to the github project.

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.. 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}

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds

Reply via email to