Re: Another test failure which is not related to the tested patch
- Original Message - From: ybronhei ybron...@redhat.com To: Dan Kenigsberg dan...@redhat.com, Sandro Bonazzola sbona...@redhat.com, ykap...@redhat.com Cc: Eyal Edri ee...@redhat.com, infra infra@ovirt.org Sent: Monday, June 8, 2015 6:59:40 PM Subject: Re: Another test failure which is not related to the tested patch On 06/08/2015 03:39 PM, Dan Kenigsberg wrote: On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote: Il 06/06/2015 11:57, Eyal Edri ha scritto: Hi, thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them. i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel? We can't disable epel testing since ioprocess is not yet in stable repo. (btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess ) Its just clicking in the package page title push to stable so I did it probably it will be there in few days sandro, after these are published, can we drop the testing repos from the mock jobs? -- Yaniv Bronhaim. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization RD Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Another test failure which is not related to the tested patch
Il 09/06/2015 10:02, Eyal Edri ha scritto: - Original Message - From: ybronhei ybron...@redhat.com To: Dan Kenigsberg dan...@redhat.com, Sandro Bonazzola sbona...@redhat.com, ykap...@redhat.com Cc: Eyal Edri ee...@redhat.com, infra infra@ovirt.org Sent: Monday, June 8, 2015 6:59:40 PM Subject: Re: Another test failure which is not related to the tested patch On 06/08/2015 03:39 PM, Dan Kenigsberg wrote: On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote: Il 06/06/2015 11:57, Eyal Edri ha scritto: Hi, thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them. i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel? We can't disable epel testing since ioprocess is not yet in stable repo. (btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess ) Its just clicking in the package page title push to stable so I did it probably it will be there in few days sandro, after these are published, can we drop the testing repos from the mock jobs? We can try and see if something is missing. I've not all the requirments for all the packages at hand. -- Yaniv Bronhaim. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: engine-patches mailing list
On 06/09/2015 02:45 PM, Omer Frenkel wrote: - Original Message - From: David Caro dcaro...@redhat.com To: Omer Frenkel ofren...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, June 9, 2015 2:19:42 PM Subject: Re: engine-patches mailing list On 06/09, Omer Frenkel wrote: Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html how this affect the engine-patches mailing list administration? David why is engine-patches is needed at all? gerrit hooks are the one who triggers ci jobs no? ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: engine-patches mailing list
- Original Message - From: David Caro dcaro...@redhat.com To: Omer Frenkel ofren...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, June 9, 2015 2:19:42 PM Subject: Re: engine-patches mailing list On 06/09, Omer Frenkel wrote: Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html how this affect the engine-patches mailing list administration? ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: engine-patches mailing list
On 06/09, Omer Frenkel wrote: - Original Message - From: David Caro dcaro...@redhat.com To: Omer Frenkel ofren...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, June 9, 2015 2:19:42 PM Subject: Re: engine-patches mailing list On 06/09, Omer Frenkel wrote: Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html how this affect the engine-patches mailing list administration? This affects the patch review process giving an alternative to subscribing to that list and easily getting that info from the ui or filtering it out. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpmCdqq5tab0.pgp Description: PGP signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
engine-patches mailing list
Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [urgent] call for developers - upstream jenkins: Build Queue (543) WAS: Fwd: [ovirt-devel] gerrit+ci improvement proposal
As a first contention measure to alleviate the flood, I've changed the way
findbugs is triggered to get triggered only on verified +1 (it will set code
review flag on pass or failure, and will run on drafts, can't use more than one
condition for the trigger).
On 06/09, Max Kovgan wrote:
hi, Dear Developers!
We are aware of the urge and pressure to push your patches a.s.a.p before the
code freeze.
Howeever, with current flow of patch updates, we currently have an overloaded
CI, which will result in a very long waiting time for jobs to start
SO, in order to reduce that time, please make sure you are using DRAFTs [1]
for early stage patches [during human reviews]
how to use drafts:
1) using plain git push - refer to [1]
2) using git review plugin
if you've installed git review plugin:
git review -D -r repo branch
example with repo origin and branch master:
git review -D -r origin master
plugin can be installed as explained here: [2]
[1] http://stackoverflow.com/questions/18106064/how-to-push-drafts-to-gerrit
[2] http://www.mediawiki.org/wiki/Gerrit/git-review#Fedora.2FCentOS
N.B.
Using drafts is the only alternative for adding 2 new gerrit flags.
If you have better ideas - you are still welcome to suggest.
Earlier today I did some mining on gerrit patches status:
out of ~1400 open patches ~350 are drafts, which was incouraging.
Yet out of all 66 committers for those patches only 6 are using drafts:
In [25]: for c in changes:
: if c.get('status') != 'DRAFT':
: continue
: saints.add(c.get('owner').get('name'))
:
In [26]: saints
Out[26]:
{u'Alon Bar-Lev',
u'Liron Aravot',
u'Martin Mucha',
u'Nir Soffer',
u'Piotr Kliczewski',
u'Tomer Saban'}
Kudos.
Max Kovgan
Senior Software Engineer
Red Hat - EMEA ENG Virtualization RD
Tel.: +972 9769 2060
Email: mkovgan [at] redhat [dot] com
Web: http://www.redhat.com
RHT Global #: 82-72060
- Forwarded Message -
From: Oved Ourfali oourf...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra
infra@ovirt.org
Sent: Sunday, June 7, 2015 10:05:23 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
On Jun 7, 2015 10:00 AM, Eyal Edri ee...@redhat.com wrote:
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Sunday, June 7, 2015 9:55:56 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Eli Mesika emes...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra@ovirt.org
Sent: Sunday, June 7, 2015 9:52:15 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eli Mesika emes...@redhat.com
To: Oved Ourfali ov...@redhat.com
Cc: Eyal Edri ee...@redhat.com, infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 3:49:05 PM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 10:03:02 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Sandro Bonazzola sbona...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 9:46:40 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Eyal Edri ee...@redhat.com, Max Kovgan
mkov...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 9:11:10 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
Il 03/06/2015 21:46, Eyal Edri ha scritto:
- Original Message -
From: Max Kovgan mkov...@redhat.com
To: de...@ovirt.org
Cc: infra@ovirt.org
Sent: Wednesday, June 3, 2015 8:22:54 PM
Subject: [ovirt-devel] gerrit+ci improvement proposal
Hi everyone!
We really want to have reliable and snappy CI: to allow
short
cycles
and
encourage developers to write tests.
# Problem
Many patches are neither ready for review nor for CI upon
submission,
which
is OK.
But running all the jobs on those patches with limited
resources
results
in:
overloaded resources,
[urgent] call for developers - upstream jenkins: Build Queue (543) WAS: Fwd: [ovirt-devel] gerrit+ci improvement proposal
hi, Dear Developers!
We are aware of the urge and pressure to push your patches a.s.a.p before the
code freeze.
Howeever, with current flow of patch updates, we currently have an overloaded
CI, which will result in a very long waiting time for jobs to start
SO, in order to reduce that time, please make sure you are using DRAFTs [1] for
early stage patches [during human reviews]
how to use drafts:
1) using plain git push - refer to [1]
2) using git review plugin
if you've installed git review plugin:
git review -D -r repo branch
example with repo origin and branch master:
git review -D -r origin master
plugin can be installed as explained here: [2]
[1] http://stackoverflow.com/questions/18106064/how-to-push-drafts-to-gerrit
[2] http://www.mediawiki.org/wiki/Gerrit/git-review#Fedora.2FCentOS
N.B.
Using drafts is the only alternative for adding 2 new gerrit flags.
If you have better ideas - you are still welcome to suggest.
Earlier today I did some mining on gerrit patches status:
out of ~1400 open patches ~350 are drafts, which was incouraging.
Yet out of all 66 committers for those patches only 6 are using drafts:
In [25]: for c in changes:
: if c.get('status') != 'DRAFT':
: continue
: saints.add(c.get('owner').get('name'))
:
In [26]: saints
Out[26]:
{u'Alon Bar-Lev',
u'Liron Aravot',
u'Martin Mucha',
u'Nir Soffer',
u'Piotr Kliczewski',
u'Tomer Saban'}
Kudos.
Max Kovgan
Senior Software Engineer
Red Hat - EMEA ENG Virtualization RD
Tel.: +972 9769 2060
Email: mkovgan [at] redhat [dot] com
Web: http://www.redhat.com
RHT Global #: 82-72060
- Forwarded Message -
From: Oved Ourfali oourf...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra
infra@ovirt.org
Sent: Sunday, June 7, 2015 10:05:23 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
On Jun 7, 2015 10:00 AM, Eyal Edri ee...@redhat.com wrote:
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Sunday, June 7, 2015 9:55:56 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Eli Mesika emes...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra@ovirt.org
Sent: Sunday, June 7, 2015 9:52:15 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eli Mesika emes...@redhat.com
To: Oved Ourfali ov...@redhat.com
Cc: Eyal Edri ee...@redhat.com, infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 3:49:05 PM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 10:03:02 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Sandro Bonazzola sbona...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 9:46:40 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Eyal Edri ee...@redhat.com, Max Kovgan
mkov...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 9:11:10 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
Il 03/06/2015 21:46, Eyal Edri ha scritto:
- Original Message -
From: Max Kovgan mkov...@redhat.com
To: de...@ovirt.org
Cc: infra@ovirt.org
Sent: Wednesday, June 3, 2015 8:22:54 PM
Subject: [ovirt-devel] gerrit+ci improvement proposal
Hi everyone!
We really want to have reliable and snappy CI: to allow short
cycles
and
encourage developers to write tests.
# Problem
Many patches are neither ready for review nor for CI upon
submission,
which
is OK.
But running all the jobs on those patches with limited
resources
results
in:
overloaded resources, slow response time, unhappy developers.
# Proposed Solution
To run less jobs we know we don’t need to, thus making more
resources
for
the
jobs we need to run.
We have been experimenting to make our CI stabler and quicker
to
respond
by
using gerrit flags. This has improved in both directions very
well
internally.
please review wiki change
hi. I have updated this page: http://www.ovirt.org/Working_with_oVirt_Gerrit Please review and confirm/modify. I think this page should be a goto page for gerrit instructions. I'm also planning to update it with info on how to install git-review plugin soon. Regards. Max Kovgan Senior Software Engineer Red Hat - EMEA ENG Virtualization RD Tel.: +972 9769 2060 Email: mkovgan [at] redhat [dot] com Web: http://www.redhat.com RHT Global #: 82-72060 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [urgent] call for developers - upstream jenkins: Build Queue (543) WAS: Fwd: [ovirt-devel] gerrit+ci improvement proposal
Thanks!
Max Kovgan
Senior Software Engineer
Red Hat - EMEA ENG Virtualization RD
Tel.: +972 9769 2060
Email: mkovgan [at] redhat [dot] com
Web: http://www.redhat.com
RHT Global #: 82-72060
- Original Message -
From: David Caro dcaro...@redhat.com
To: Max Kovgan mkov...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Tuesday, June 9, 2015 6:41:16 PM
Subject: Re: [urgent] call for developers - upstream jenkins: Build Queue (543)
WAS: Fwd: [ovirt-devel] gerrit+ci improvement proposal
As a first contention measure to alleviate the flood, I've changed the way
findbugs is triggered to get triggered only on verified +1 (it will set code
review flag on pass or failure, and will run on drafts, can't use more than one
condition for the trigger).
On 06/09, Max Kovgan wrote:
hi, Dear Developers!
We are aware of the urge and pressure to push your patches a.s.a.p before the
code freeze.
Howeever, with current flow of patch updates, we currently have an overloaded
CI, which will result in a very long waiting time for jobs to start
SO, in order to reduce that time, please make sure you are using DRAFTs [1]
for early stage patches [during human reviews]
how to use drafts:
1) using plain git push - refer to [1]
2) using git review plugin
if you've installed git review plugin:
git review -D -r repo branch
example with repo origin and branch master:
git review -D -r origin master
plugin can be installed as explained here: [2]
[1] http://stackoverflow.com/questions/18106064/how-to-push-drafts-to-gerrit
[2] http://www.mediawiki.org/wiki/Gerrit/git-review#Fedora.2FCentOS
N.B.
Using drafts is the only alternative for adding 2 new gerrit flags.
If you have better ideas - you are still welcome to suggest.
Earlier today I did some mining on gerrit patches status:
out of ~1400 open patches ~350 are drafts, which was incouraging.
Yet out of all 66 committers for those patches only 6 are using drafts:
In [25]: for c in changes:
: if c.get('status') != 'DRAFT':
: continue
: saints.add(c.get('owner').get('name'))
:
In [26]: saints
Out[26]:
{u'Alon Bar-Lev',
u'Liron Aravot',
u'Martin Mucha',
u'Nir Soffer',
u'Piotr Kliczewski',
u'Tomer Saban'}
Kudos.
Max Kovgan
Senior Software Engineer
Red Hat - EMEA ENG Virtualization RD
Tel.: +972 9769 2060
Email: mkovgan [at] redhat [dot] com
Web: http://www.redhat.com
RHT Global #: 82-72060
- Forwarded Message -
From: Oved Ourfali oourf...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra
infra@ovirt.org
Sent: Sunday, June 7, 2015 10:05:23 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
On Jun 7, 2015 10:00 AM, Eyal Edri ee...@redhat.com wrote:
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Sunday, June 7, 2015 9:55:56 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Eli Mesika emes...@redhat.com
Cc: Oved Ourfali ov...@redhat.com, de...@ovirt.org, infra@ovirt.org
Sent: Sunday, June 7, 2015 9:52:15 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eli Mesika emes...@redhat.com
To: Oved Ourfali ov...@redhat.com
Cc: Eyal Edri ee...@redhat.com, infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 3:49:05 PM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Oved Ourfali ov...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 10:03:02 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Eyal Edri ee...@redhat.com
To: Sandro Bonazzola sbona...@redhat.com
Cc: infra@ovirt.org, de...@ovirt.org
Sent: Thursday, June 4, 2015 9:46:40 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Eyal Edri ee...@redhat.com, Max Kovgan
mkov...@redhat.com
Cc: de...@ovirt.org, infra@ovirt.org
Sent: Thursday, June 4, 2015 9:11:10 AM
Subject: Re: [ovirt-devel] gerrit+ci improvement proposal
Il 03/06/2015 21:46, Eyal Edri ha scritto:
- Original Message -
From: Max Kovgan mkov...@redhat.com
To: de...@ovirt.org
Cc: infra@ovirt.org
Sent: Wednesday, June 3, 2015 8:22:54 PM
Subject: [ovirt-devel] gerrit+ci improvement proposal
Re: engine-patches mailing list
On 06/09/2015 03:22 PM, David Caro wrote: On 06/09, Roy Golan wrote: On 06/09/2015 02:45 PM, Omer Frenkel wrote: - Original Message - From: David Caro dcaro...@redhat.com To: Omer Frenkel ofren...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, June 9, 2015 2:19:42 PM Subject: Re: engine-patches mailing list On 06/09, Omer Frenkel wrote: Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html how this affect the engine-patches mailing list administration? David why is engine-patches is needed at all? gerrit hooks are the one who triggers ci jobs no? That seems a common misunderstanding, the gerrit hooks are not related to jenkins, jenkins connects to gerrit itself (has stream access) independently of the hooks. Clarified that, not sure why engine-patches is needed but I think itamar and some team leads use it to monitor activity. Though afaik that can be done subscribing to the project (maibe that feature was not available on gerrit before) True, it wasn't and mails where used for code-review and monitoring. So all subscribers must know how to subscribe to mail from the gerrit personal settings [1] and engine-patches should be deprecated [1] https://gerrit.ovirt.org/#/settings/projects ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: engine-patches mailing list
On 06/09, Roy Golan wrote: On 06/09/2015 02:45 PM, Omer Frenkel wrote: - Original Message - From: David Caro dcaro...@redhat.com To: Omer Frenkel ofren...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, June 9, 2015 2:19:42 PM Subject: Re: engine-patches mailing list On 06/09, Omer Frenkel wrote: Hi, I've been monitoring the pending requests list for the engine-patches mailing list for a while now, from what i could see, no one send mails to this list except automated mails initiated at gerrit (which is pretty much expected). the rest is spam.. this makes a requirement for people using gerrit (code contributors and reviewers) to subscribe to the list, and get all the mails on all gerrit activity. some people do not want to subscribe, and mails on their activity needs manual processing. maybe there is a way to have automated job to run daily/weekly to add all gerrit users to the accept list for this list? then i would change the list to automatically reject all mail from non-subscribers and users that are not in the accept list. what do you think? any other suggestion? see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html how this affect the engine-patches mailing list administration? David why is engine-patches is needed at all? gerrit hooks are the one who triggers ci jobs no? That seems a common misunderstanding, the gerrit hooks are not related to jenkins, jenkins connects to gerrit itself (has stream access) independently of the hooks. Clarified that, not sure why engine-patches is needed but I think itamar and some team leads use it to monitor activity. Though afaik that can be done subscribing to the project (maibe that feature was not available on gerrit before) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpp8CXl_WSUv.pgp Description: PGP signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
