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

3 views
Skip to first unread message

brian.murrell@intel.com (JIRA)

unread,
Mar 4, 2019, 2:45:02 PM3/4/19
to jenkinsc...@googlegroups.com
Brian J Murrell created an issue
 
Jenkins / Improvement JENKINS-56395
Expose "trusted" attribute of a PR to the Pipeline
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: github-branch-source-plugin
Created: 2019-03-04 19:44
Priority: Major Major
Reporter: Brian J Murrell

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.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

craigbarber@google.com (JIRA)

unread,
Jul 25, 2019, 3:53:02 PM7/25/19
to jenkinsc...@googlegroups.com
Craig Barber commented on Improvement JENKINS-56395
 
Re: Expose "trusted" attribute of a PR to the Pipeline

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

bitwiseman@gmail.com (JIRA)

unread,
May 5, 2020, 7:27:02 PM5/5/20
to jenkinsc...@googlegroups.com

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

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

brian.murrell@intel.com (JIRA)

unread,
May 6, 2020, 7:40:02 AM5/6/20
to jenkinsc...@googlegroups.com

Craig Barber 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.

Reply all
Reply to author
Forward
0 new messages