ghprb-plugin
ghprb-plugin copied to clipboard
Handle (un)labeled pull request hooks
Without handling the unlabeled
hook jenkins still things the ignore label is present (#431) and skips building the PR.
This might also fix #496.
I assume you made a manual test of this?
Although this solved the issue with removing blacklist labels, I just noticed that adding new labels to a PR after it was merged, caused it to be rebuild. I'll investigate a fix for that behaviour and update the PR.
see http://jenkins.kodi.tv/view/Automation/job/BuildMulti-PR/7295/ http://jenkins.kodi.tv/view/Automation/job/BuildMulti-PR/7296/
Thanks!
any update on this?
Would love to get this change in. List of GitHub labels for which the build should not be triggered
works but if labels are removed, builds still won't be triggered
@Rechi do you have an update on your issue?
Also wondering when it will be merged?
Sorry for the extra comment, but I'm really interested in having this change merged.
+1 to this feature as well!
It looks good enough to me, even if there are some edge cases that might still not be covered, most of them are.
+1 too
@Rechi I tried to build your edits and added the plugin manually to jenkins but still changes labels couldn't be triggered by jenkins
Hi all, is there anything I can do to help move this forward? We'd love to utilize this feature in our workflow. Thanks!
@janinko I really would like to get your opinion on this PR
My team strongly relies on label events to trigger builds. Can you consider accepting and merging the pull request as it is (with conflict fixes)? I would prefer not to fork your project in order to get this functionality working.
If the pull request needs any fixes, I would be happy to take care of them.
Even though I'm the original author of this plugin, I'm not its maintainer anymore for a long time. If there are no active maintainer I suggest to look at https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/
@janinko I really appreciate you getting back about this! It's understandable if you don't want to maintain the plugin.
@bjoernhaeuser Are you also no longer an active maintainer?
@janinko In the off chance that this PR is acceptable, I'm going to file a duplicate PR that addresses comments and fixes the merge conflict.