[JIRA] (OVIRT-1617) Please add Mark Chappell (mchappel) to CI whitelist

28 Aug 2017

      This is a multi-part message in MIME format...

------------=_1503920554-15592-143
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34800#comment-34800 ] 

eyal edri commented on OVIRT-1617:
----------------------------------

Hi,

[~omachace@redhat.com] I just want to emphasise something important to understand around how the whitelist works in CI.
The normal 'jenkins whitelist' we know is only relevant for Gerrit projects and there we maintain a list of whitelisted emails of contributros which are allowed
to run tests on Jenkins.

It not relevant when it comes to GitHub projects, because the whitelisting mechanism there is different. 
For adding a new contributor to the project in GitHub, you need to invite him into the project ( as project admin in GitHub ), via the GitHub UI.
So as admin you can actually do it and you don't require our help in most cases.

Only if we want to add a contributor to ALL oVirt projects, then we need to add him to the oVirt org, and you need to be admin to do it.

Can you try and invite 'tremble' user to the ovirt-ansible project and see how it goes?
...
Please add Mark Chappell (mchappel) to CI whitelist
---------------------------------------------------
Key: OVIRT-1617
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1617
            Project: oVirt - virtualization made easy
         Issue Type: Task
         Components: oVirt Infra
           Reporter: Ondra Machacek
           Assignee: infra
Hi,
please add Mark Chappell (mchappel) to ovirt-ansible CI whitelist.
Thanks.
--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)

------------=_1503920554-15592-143
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1617?page=com.atlassian.jira.p... ]</pre>
<h3>eyal edri commented on OVIRT-1617:</h3>
<p>Hi,</p>
<p>[~omachace@redhat.com] I just want to emphasise something important to understand around how the whitelist works in CI. The normal ‘jenkins whitelist’ we know is only relevant for Gerrit projects and there we maintain a list of whitelisted emails of contributros which are allowed to run tests on Jenkins.</p>
<p>It not relevant when it comes to GitHub projects, because the whitelisting mechanism there is different. For adding a new contributor to the project in GitHub, you need to invite him into the project ( as project admin in GitHub ), via the GitHub UI. So as admin you can actually do it and you don't require our help in most cases.</p>
<p>Only if we want to add a contributor to ALL oVirt projects, then we need to add him to the oVirt org, and you need to be admin to do it.</p>
<p>Can you try and invite ‘tremble’ user to the ovirt-ansible project and see how it goes?</p>
<blockquote><h3>Please add Mark Chappell (mchappel) to CI whitelist</h3>
<pre>     Key: OVIRT-1617
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1617
 Project: oVirt - virtualization made easy
         Issue Type: Task
         Components: oVirt Infra
Reporter: Ondra Machacek
Assignee: infra</pre>
<p>Hi, please add Mark Chappell (mchappel) to ovirt-ansible CI whitelist. Thanks.</p></blockquote>
<p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." 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>

------------=_1503920554-15592-143--

eyal edri (oVirt JIRA)

tags

participants (1)