limit the amount of warnings the whitelist bots sends to GitHub


I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: - on 1 commits there were 13 alerts.


Barak Korren
September 17, 2017, 8:47 AM

All code required to avoid spamming PRs had been merged as part of work on OVIRT-1522.

Barak Korren
August 6, 2017, 9:12 AM

We considered too possible solutions for this:

  1. Not use the built-in whitelist functionality of the PR-builder plugin, and use our existing whitelist file instead.

  2. Re-engineer things so that we will only have a single job that is configured with the PR-builder plugin.

Option #1 will probably not be popular with developers its also might not be even possible to implement this because it seems that Github does not expose the email addresses of contributors to Jenkins while out whilelist file is based on email addresses.

Option #2 essentially means implementing OVIRT-1522, so setting it as a blocker for this.

Barak Korren
July 23, 2017, 6:32 AM

There is no bot here.

This seems to be the logic on the GitHub pull-request trigger plugin when if is configured to filter by project/organisation membership.
I suspect the amount of alerts matches the amount of jobs we have triggering on pull request events exactly.

We probably need a staging environment for further testing and coming up with solutions, so adding as a blocker



Barak Korren


Eyal Edri

Blocked By