This is a multi-part message in MIME format...
------------=_1505835477-31751-486
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jir...
]
Barak Korren reassigned OVIRT-1657:
-----------------------------------
Assignee: Barak Korren (was: infra)
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: Barak Korren
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)
------------=_1505835477-31751-486
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jir...
]</pre>
<h3>Barak Korren reassigned OVIRT-1657:</h3>
<pre>Assignee: Barak Korren (was: infra)</pre>
<blockquote><h3>Unity CI whitelist mechanism for GitHub and Gerrit</h3>
<pre> 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: Barak Korren</pre>
<p>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:</p>
<ul><li><p>Its impossible for maintainers to manually override
it</p></li>
<li><p>Maintainers hate to send patches to an unrelated
repo</p></li>
<li><p>Its impossible to have a per-project
whitelist</p></li></ul>
<p>The GitHub style whitelist has a few shortcomings as well:</p>
<ul><li><p>Whitelist members that were added via comments on PRs are
stored in the job configuration and can vanish if jobs are updated via
JJB</p></li>
<li><p>The GHPRB plugin forces us to create jobs in a very specific way (One
job per project)</p></li>
<li><p>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).</p></li></ul></blockquote>
<p>— This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)</p>
<img
src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpS...
alt="" width="1" height="1" border="0"
style="height:1px !important;width:1px !important;border-width:0
!important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0
!important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0
!important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1505835477-31751-486--