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

Expose "trusted" attribute of a PR to the Pipeline

      It would be very useful in a Pipeline job to be able to know the value of the Trusted attribute for a PR so that the Pipeline could handle it differently based on whether it came from a trusted source or not.

          [JENKINS-56395] Expose "trusted" attribute of a PR to the Pipeline

          Craig Barber added a comment -

          +1 to this. Being able to filter so that jobs only get triggered on PRs submitted by trusted contributors would eliminate a major abuse vector currently exposed by the plugin.

          Craig Barber added a comment - +1 to this. Being able to filter so that jobs only get triggered on PRs submitted by trusted contributors would eliminate a major abuse vector currently exposed by the plugin.

          Liam Newman added a comment -

          Please come discuss on https://gitter.im/jenkinsci/github-branch-source-plugin . Happy to point someone in the right direction to implement this.

          Liam Newman added a comment - Please come discuss on https://gitter.im/jenkinsci/github-branch-source-plugin . Happy to point someone in the right direction to implement this.

          craigbarber Your desire for this appears to be the same as mine – to build into my {{Jenkinsfile}}s the ability to prevent non-trusted people's PRs from being run through our CI.  The irony of this whole ticket is that while this functionality could be useful for other reasons, we are desiring it simply because the mechanisms built into Jenkins that are supposed to provide this functionality are simply broken.  If they worked, I wouldn't have opened this ticket.

          Brian J Murrell added a comment - craigbarber Your desire for this appears to be the same as mine – to build into my {{Jenkinsfile}}s the ability to prevent non-trusted people's PRs from being run through our CI.  The irony of this whole ticket is that while this functionality could be useful for other reasons, we are desiring it simply because the mechanisms built into Jenkins that are supposed to provide this functionality are simply broken.  If they worked, I wouldn't have opened this ticket.

            Unassigned Unassigned
            brianjmurrell Brian J Murrell
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: