Johnny Bieren created OVIRT-3080:
Summary: Add jbieren to jenkins-whitelist
Key: OVIRT-3080
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3080
Project: oVirt - virtualization made easy
Krapali Rai created OVIRT-3072:
--
Summary: To add Romain Arnaud to the jenkins-whitelist
Key: OVIRT-3072
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3072
Project: oVirt - virtualization made easy
h does not run
>>>>>>>> with
>>>>>>>> this change,
>>>>>>>> even when I trigger the tests manually with "ci test".
>>>>>>>>
>>>>>>>> I tried to add +1 for "RHEL-
gt;>>>>
>>>>>>> RHEL-Continuous-Integration You don't have permission to edit
>>>>>>> this label.
>>>>>>>
>>>>>>
>>>>> I cannot merge anything as well. I wonder why maintainers don't
-Continuous-Integration You don't have permission to edit
>>>>>> this label.
>>>>>>
>>>>>
>>>> I cannot merge anything as well. I wonder why maintainers don't get the
>>>> permission
>>>> for the new flag? Ap
he new flag? Apparently the automation for this is not working
>>> yet.
>>>
>>>
>>>>
>>>>> So finally I downloaded the patch and pushed it manually.
>>>>>
>>>>> I think this patch will fix the
flag? Apparently the automation for this is not working yet.
>>
>>
>>>
>>>> So finally I downloaded the patch and pushed it manually.
>>>>
>>>> I think this patch will fix the problem:
>>>> https://gerrit.ovirt.org/#/c/
> for the new flag? Apparently the automation for this is not working yet.
>
>
>>
>>> So finally I downloaded the patch and pushed it manually.
>>>
>>> I think this patch will fix the problem:
>>> https://gerrit.ovirt.org/#/c/110576/
>>>
&g
orking yet.
>
>> So finally I downloaded the patch and pushed it manually.
>>
>> I think this patch will fix the problem:
>> https://gerrit.ovirt.org/#/c/110576/
>>
>> But I need CI experts to review this. Since we have 50 projects that need
>> this,
&g
and inherited by all projects.
>
> I know that Germano was not able to trigger tests because he was missing
> in the
> jenkins whitelist, but this was fixed last week.
>
> Germano, maybe just to check that everything works for you, you can post
> some
> trivial patch?
&
d
> this,
> this probably should be fixed elsewhere, and inherited by all projects.
>
> I know that Germano was not able to trigger tests because he was missing in
> the
> jenkins whitelist, but this was fixed last week.
>
> Germano, maybe just to check that everything works
/#/c/110576/
But I need CI experts to review this. Since we have 50 projects that need this,
this probably should be fixed elsewhere, and inherited by all projects.
I know that Germano was not able to trigger tests because he was missing in the
jenkins whitelist, but this was fixed last week.
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Marchukov closed OVIRT-2662.
--
Makes sense. Closing
> jenkins whitelist issue in ovirt-web
at a user can be added to the oVirt org or the project
if we want to add him permenantly for whitelisting.
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-jira.atlassian.ne
ntly handling it or somebody else have to? I
see this is in progress but no owner.
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662
>
user also gets permissions to all
other projects along the way, and its also something the project maintainers
are not supposed to be able to do.
It would be best if we could find something that:
# Permanently affects a single project
# Can be easily done by maintainers.
> jenkins whitelist i
the user to the oVirt org as a
permanent solution since the whitelist can be removed as you say, until we'll
have something permanent.
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
>
ere issues and improvements to the whitelist
mechanism have been discussed in the past:
* OVIRT-1154
* OVIRT-1657
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-jira.at
o be part of the oVirt ORG
first before he can be added to whitelist with the 'add to whitelist' or its a
bug we need to investigate?
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
>
pdate the msg...
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662
> Project: oVirt - virtualization made easy
>
the user also has to be part of the oVirt org" -- that should be in
the bot's message, then :)
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-ji
next week. I suggest to look
at the logs in the webhooks to see what's happening.
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662
&
mes. Next time he opens a PR, it will likely
happen again.
For example:
https://github.com/oVirt/ovirt-web-ui/pull/904 why didn't that work? Why did
he get it again on PR 931?
> jenkins whitelist issue in ovirt-web-ui
> ---
>
>
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Sheremeta reopened OVIRT-2662:
---
> jenkins whitelist issue in ovirt-web
maintainer needs to write "ci add to whitelist" in order to allow the PR to
run CI.
I've just done it to the PR and it started running in CI
> jenkins whitelist issue in ovirt-web-ui
> ---
>
> Key: OVIRT-2662
>
ributors." The bot is lying -- it ran the tests, and
I have 'add to whitelist' for Bohdan several times now.
How do we cure this?
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gsher...@redhat.com IRC: gshereme
<
Greg Sheremeta created OVIRT-2662:
-
Summary: jenkins whitelist issue in ovirt-web-ui
Key: OVIRT-2662
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662
Project: oVirt - virtualization made easy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Edri closed OVIRT-2544.
Resolution: Fixed
> Please add Victor to the jenkins whitel
the jenkins whitelist
> --
>
> Key: OVIRT-2544
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2544
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>
Victor to the jenkins whitelist
> --
>
> Key: OVIRT-2544
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2544
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
&
Nir Soffer created OVIRT-2544:
-
Summary: Please add Victor to the jenkins whitelist
Key: OVIRT-2544
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2544
Project: oVirt - virtualization made easy
Hi infra team,
We got a this patch from Victor Stinner :
https://gerrit.ovirt.org/#/c/94974/
Since his email address is not in jenkins whiteslit, the CI does not run
the tests with this message:
No Builds Executed
http://jenkins.ovirt.org/job/pthreading_master_check-patch-fc27-x86_64/3/ :
To a
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Edri updated OVIRT-2442:
-
Resolution: Fixed
Status: Done (was: To Do)
> Re: [jenkins-whitelist] add a user to whitel
this is done
https://gerrit.ovirt.org/#/c/93818/ [1]
> Re: [jenkins-whitelist] add a user to whitelist
> ---
>
> Key: OVIRT-2442
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2442
>
Eyal Edri created OVIRT-2442:
Summary: Re: [jenkins-whitelist] add a user to whitelist
Key: OVIRT-2442
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2442
Project: oVirt - virtualization made easy
sending to infra-support to open a ticket.
On Mon, Aug 20, 2018 at 3:57 PM Marcin Sobczyk wrote:
> Hi,
> I've just started working on vdsm project. Can someone please add me to CI
> whitelist?
> Thanks, Marcin
> ___
> Infra mailing list -- infra@ovirt.
Hi,
I've just started working on vdsm project. Can someone please add me to CI
whitelist?
Thanks, Marcin
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Epic Link: (was: OVIRT-400)
> Improve and automate the jenkins-whitelist mechan
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Component/s: Standard CI (Pipelines)
> Improve and automate the jenkins-whitelist mechan
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Epic Link: (was: OVIRT-400)
> Improve and automate the jenkins-whitelist mechan
I see you are writing from mduar...@redhat.com, but in gerrit I see
mdbarr...@redhat.com.
Is mdbarr...@redhat.com the right email address to be added?
Please add yourself to
https://gerrit.ovirt.org/#/admin/projects/jenkins-whitelist ; feel free to
add me as reviewer.
2018-05-09 17:02 GMT+02:00
d?..
>
> Regards,
> Miguel
>
>
> On Wed, May 9, 2018 at 5:39 PM, Barak Korren wrote:
> > forwarding to infra-support to create a Jira ticket.
> >
> > -- Forwarded message ------
> > From: Miguel Duarte de Mora Barroso
> > Date: 9 May 2018 at 18
add me to gerrit jenkins whitelist
> ---
>
> Key: OVIRT-2012
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2012
> Project: oVirt - virtualization made easy
> Issue Type: Task
>
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-2012:
Epic Link: OVIRT-403
> Fwd: add me to gerrit jenkins whitel
en
>Assignee: infra
>
> forwarding to infra-support to create a Jira ticket.
> -- Forwarded message --
> From: Miguel Duarte de Mora Barroso
> Date: 9 May 2018 at 18:02
> Subject: add me to gerrit jenkins whitelist
> To: infra@ovirt.org
> Hi,
Barak Korren created OVIRT-2012:
---
Summary: Fwd: add me to gerrit jenkins whitelist
Key: OVIRT-2012
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2012
Project: oVirt - virtualization made easy
Hi,
I'm a new hire for redhat and will be working in ovirt networking.
I'll need to be added to the jenkins CI whitelist.
Do you need any further information?
Regards,
Miguel
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to in
to Jenkins whitelist
>
>
> Key: OVIRT-1865
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1865
> Project: oVirt - virtualization made easy
> Issue Type: Task
>Reporter: Israel Pin
Israel Pinto created OVIRT-1865:
---
Summary: Add me to Jenkins whitelist
Key: OVIRT-1865
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1865
Project: oVirt - virtualization made easy
Issue
.
> Re: Jenkins Whitelist
> -
>
> Key: OVIRT-1353
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1353
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>Reporter: Barak Korr
> Re: Jenkins Whitelist
> -
>
> Key: OVIRT-1353
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1353
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>Reporter: Barak
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Shinar reassigned OVIRT-1353:
-
Assignee: Evgheni Dereveanchin (was: infra)
> Re: Jenkins Whitel
Barak Korren created OVIRT-1353:
---
Summary: Re: Jenkins Whitelist
Key: OVIRT-1353
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1353
Project: oVirt - virtualization made easy
Issue Type
Adding infra-support to open a Jira ticket.
On 27 April 2017 at 12:21, Miroslava Voglova wrote:
> Hi,
>
> I got this error:
>
> No Builds Executed
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/22563/
> : To avoid overloading the infrastructure, a whitelist for
> runn
Hi,
I got this error:
No Builds Executed
http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
-el7-x86_64/22563/ : To avoid overloading the infrastructure, a whitelist
for
running gerrit triggered jobs has been set in place, if
you feel like you should be in it, please contact infra at
o
nt-27649
> Improve and automate the jenkins-whitelist mechanism
>
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made
ger
> it directly in the message
>
> It all basically boils down to "Do not make me think" approach.
> Everything that needs to be done is immediately obvious without
> searching. And that I could accept even with the whitel
cked.
> Addition to the Jenkins whitelist
> -
>
> Key: OVIRT-1191
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1191
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1191:
---
Assignee: Barak Korren (was: infra)
> Addition to the Jenkins whitel
Benny Zlotnik created OVIRT-1191:
Summary: Addition to the Jenkins whitelist
Key: OVIRT-1191
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1191
Project: oVirt - virtualization made easy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1186:
---
Assignee: Barak Korren (was: infra)
> jenkins whitelist addit
Leon Goldberg created OVIRT-1186:
Summary: jenkins whitelist addition
Key: OVIRT-1186
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1186
Project: oVirt - virtualization made easy
Issue
Yevgeny Zaspitsky created OVIRT-1184:
Summary: ovirt jenkins whitelist
Key: OVIRT-1184
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1184
Project: oVirt - virtualization made easy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomo Ben David reassigned OVIRT-1184:
---
Assignee: Shlomo Ben David (was: infra)
> ovirt jenkins whitel
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1177:
---
Assignee: Barak Korren (was: infra)
> Please add emarc...@redhat.com to jenkins whitel
ters to have their code checked.
I think we should probably most of the various ideas raised here rather then
just picking one or the other. One reason to do that for example is that some
maintainers may prefer seeing the output of CI prior to setting CR+1.
> Improve and automate the
rgolan created OVIRT-1177:
-
Summary: Please add emarc...@redhat.com to jenkins whitelist
Key: OVIRT-1177
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1177
Project: oVirt - virtualization made easy
is a good idea anyway. Though I'm not
sure whther the actual list of maintainers is truly up to date and easy to
getbut if it is it does sound good enough if the previously mentioned
method of git log is not feasible
> Improve and automate the jenkins-whiteli
om a maintainer?
> Improve and automate the jenkins-whitelist mechanism
>
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made
something like those "ci build" comments then please
no. I never remember what's the right abracadabra magic wordit just sucks
> Improve and automate the jenkins-whitelist mechanism
>
>
> Key: OVIRT-
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Summary: Improve and automate the jenkins-whitelist mecahnism (was: Make
jenkins-whitelist use
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Summary: Improve and automate the jenkins-whitelist mechanism (was:
Improve and automate the
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomo Ben David updated OVIRT-1176:
Resolution: Fixed
Status: Done (was: To Do)
> [jenkins-whitelist] add user
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomo Ben David updated OVIRT-1176:
Summary: [jenkins-whitelist] add user to jenkins whitelist (was: Re:
Jenkins whitelist
8 PM:
--
email: dchap...@redhat.com
patch [72809|https://gerrit.ovirt.org/#/c/72809] is ready.
current status: waiting for CR
was (Author: sbend...@redhat.com):
email:
patch [72809|https://gerrit.ovirt.org/#/c/72809] is ready.
current status: waiting for CR
> Re: Jenkins wh
ttps://gerrit.ovirt.org/#/c/72809] is ready.
current status: waiting for CR
> Re: Jenkins whitelist
> -
>
> Key: OVIRT-1176
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1176
> Project: oVirt - virtualization made easy
>
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomo Ben David reassigned OVIRT-1176:
---
Assignee: Shlomo Ben David (was: infra)
> Re: Jenkins whitel
: [jenkins-whitelist] add me to the CI white list (was: Fwd:
Please add me to the CI white list)
> [jenkins-whitelist] add me to the CI white list
> ---
>
> Key: OVIRT-1175
> URL: https://ovirt-jira.atlas
Adding infra-support to open a ticket
On Tue, Feb 21, 2017 at 6:38 PM, Denis Chaplygin
wrote:
> Hello!
>
> I suppose i should be in whitelist:
>
> Patch Set 1:
>
> No Builds Executed
>
> http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_c
> heck-patch-el7-x86_64/139/ : To avoid overload
Gil Shinar created OVIRT-1176:
-
Summary: Re: Jenkins whitelist
Key: OVIRT-1176
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1176
Project: oVirt - virtualization made easy
Issue Type: By
Hello!
I suppose i should be in whitelist:
Patch Set 1:
No Builds Executed
http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_
check-patch-el7-x86_64/139/ : To avoid overloading the infrastructure, a
whitelist for
running gerrit triggered jobs has been set in place, if
you feel like you
mewhere' should probably just be a Gerrit group
(Can it be? Need to check how easy is it to map emails to Gerrit users in
practice).
It may be more useful to somehow let maintainers (know contributors?) "confirm"
a patch so that CI will check it, like we do for Lago.
for us ahead of time.
We also need some proper definition of who is considered a contributor. I don't
think that someone with a merged patch ever is a good heuristic, should
probably be something like N patches merged in the last M months.
> Make jenkins-whitelist use Gerrit groups
tors should be cached and refreshed e.g. once a
day
- single merged patch should be good enough, maybe not the whole history
indeed, perhaps last 2 years would be ok
> Make jenkins-whitelist use Gerrit groups
>
>
>
e proper definition of who is considered a contributor. I don't
think that someone with a merged patch ever is a good heuristic, should
probably be something like N patches merged in the last M months.
> Make jenkins-whitelist use Gerrit groups
>
tors rather than only maintainers
> Make jenkins-whitelist use Gerrit groups
>
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made
Barak Korren created OVIRT-1154:
---
Summary: Make jenkins-whitelist use Gerrit groups
Key: OVIRT-1154
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
Project: oVirt - virtualization made easy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1154:
Epic Link: OVIRT-400
> Make jenkins-whitelist use Gerrit gro
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1153:
---
Assignee: Barak Korren (was: infra)
> Ensure standard-CI uses the jenkins-whitel
ttps://gerrit.ovirt.org/#/c/72402/
Need to also alert developers before merging
> Ensure standard-CI uses the jenkins-whitelist
> -
>
> Key: OVIRT-1153
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153
&g
Barak Korren created OVIRT-1153:
---
Summary: Ensure standard-CI uses the jenkins-whitelist
Key: OVIRT-1153
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153
Project: oVirt - virtualization made easy
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1153:
Epic Link: OVIRT-400
> Ensure standard-CI uses the jenkins-whitel
t
Eyal.
- Original Message -
From: "Gustavo Frederico Temple Pedrosa"
To: infra@ovirt.org
Sent: Tuesday, November 5, 2013 9:23:14 PM
Subject: Jenkins Whitelist
Hello all,
How can I add the users of my team in the jenkins-whitelist?
14 PM
> Subject: Jenkins Whitelist
>
>
>
> Hello all,
>
>
>
> How can I add the users of my team in the jenkins-whitelist?
>
>
>
>
>
> Thank you very much.
>
> ___
> Infra
Hello all,
How can I add the users of my team in the jenkins-whitelist?
Thank you very much.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
talked about was the best way to manage the list and the
consensus was to use gerrit since the list could be manger without
having to have a infra team member edit the file every time we wanted to
add a new users.
jenkins-whitelist is your gerrit repo
you and eyal are currently 'maintainers
Itamar,
I need a new Gerrit repo created for the whitelist. It was talked about
on the infra list about how to manage the whitelist of users who patches
would get auto-reviewed and it was decided to run a white list. Also
what was being talked about was the best way to manage the list and th
97 matches
Mail list logo
