[ https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barak Korren updated OVIRT-1657:

Epic Link: OVIRT-400

Unity CI whitelist mechanism for GitHub and Gerrit

     Key: OVIRT-1657
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1657
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
Reporter: Barak Korren
Assignee: infra

Right now we have two separate CI mechanisms: # A mechanism based on the ‘{{jenkins-whitelist}}’ repository that is used by CI jobs for Gerrit projects # A mechanism that is part of the ‘GitHub pull request builder’ plugin that is used for GitHub based projects. The ‘{{jenkins-whitelist}}’ has a few shortcomings:

• Its impossible for maintainers to manually override it

• Maintainers hate to send patches to an unrelated repo

• Its impossible to have a per-project whitelist

The GitHub style whitelist has a few shortcomings as well:

• Whitelist members that were added via comments on PRs are stored in the job configuration and can vanish if jobs are updated via JJB

• The GHPRB plugin forces us to create jobs in a very specific way (One job per project)

• The whitelist can prevent GitHub events without specific people behind them from triggering the jobs – For example jobs are not triggered when commits are added to an existing PR because such events are sent by the ‘null’ user whihc typically is not in the whitelist… (This is probably a bug with the plugin).

— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)