Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45359

Collaborator with write access is said to not be trusted in the first PR when the project doesn't have a Jenkinsfile yet

    XMLWordPrintable

Details

    Description

      All the symptoms are the same as in https://issues.jenkins-ci.org/browse/JENKINS-40652.

      I have a repository without a `Jenkinsfile`, there is an user with write access to it that creates a PR from a branch in the same repo and jenkins doesn't pick it up, saying:

        Getting remote pull request #6379...
      
          Checking pull request #6379
          (not from a trusted source)
          Job name: PR-6379
            ‘Jenkinsfile’ not found
          Does not meet criteria
      
        1 pull requests were processed
      

      If the user created the PR from a branch in his fork, then it works perfectly.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              lucasocio Leandro Lucarella
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: