[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

0 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Aug 14, 2019, 12:54:02 PM8/14/19
to jenkinsc...@googlegroups.com
Oleg Nenashev created an issue
 
Jenkins / New Feature JENKINS-58939
Allow skipping pull requests by labels
Issue Type: New Feature New Feature
Assignee: Unassigned
Components: github-branch-source-plugin
Created: 2019-08-14 16:53
Priority: Minor Minor
Reporter: Oleg Nenashev

See INFRA-1633 for a real use-case on ci.jenkins.io. Some pull requests are stale OR contain no content to rebuild, and it does not make sense to run CI against them and to consume resources each time builds are retriggered.

I suggest adding a new trait which allows skipping pull requests if they are labeled by "skip-ci" or such labels

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

o.v.nenashev@gmail.com (JIRA)

unread,
Aug 14, 2019, 12:54:02 PM8/14/19
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Oleg Nenashev
Change By: Oleg Nenashev
Assignee: Oleg Nenashev

o.v.nenashev@gmail.com (JIRA)

unread,
Aug 14, 2019, 12:55:01 PM8/14/19
to jenkinsc...@googlegroups.com
Oleg Nenashev started work on New Feature JENKINS-58939
 
Change By: Oleg Nenashev
Status: Open In Progress

jglick@cloudbees.com (JIRA)

unread,
Aug 14, 2019, 1:06:02 PM8/14/19
to jenkinsc...@googlegroups.com
Jesse Glick commented on New Feature JENKINS-58939
 
Re: Allow skipping pull requests by labels

This can be done in a separate plugin implementing a BranchBuildStrategy, I think. Perhaps better done in scm-trait-commit-skip-plugin.

o.v.nenashev@gmail.com (JIRA)

unread,
Aug 14, 2019, 1:11:02 PM8/14/19
to jenkinsc...@googlegroups.com

stevengfoster@gmail.com (JIRA)

unread,
Aug 14, 2019, 7:02:02 PM8/14/19
to jenkinsc...@googlegroups.com

I wrote a plugin to do this for myself a long time ago, never got to publishing it because I couldn't hook up an event subscriber thing for github pull request label events. My use case was for opting-in pull requets based on label but I think I wrote the excluding case as well. I can throw what I have on github tomorrow.

https://issues.jenkins-ci.org/browse/JENKINS-50323 somewhat related.

Reply all
Reply to author
Forward
0 new messages