Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

k". > > Bob > > > -Original Message- > > From: Jay Pipes [mailto:jaypi...@gmail.com] > > Sent: 20 November 2015 21:36 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI > &

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

ld be "fuel: recheck". Bob > -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: 20 November 2015 21:36 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI > jobs >

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

+1 for "refuel" to trigger Fuel CI only, awesome idea. "recheck" will trigger both. 2015-11-20 21:12 GMT+07:00 Sergey Vasilenko : > > On Fri, Nov 20, 2015 at 4:00 PM, Alexey Shtokolov > wrote: > >> Probably we should use another keyword for

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Alexey, First of all, “refuel” sounds very cool. Thanks for raising this topic, I would like to hear more opinions here. On one hand, different keyword would help to prevent unnecessary infrastructure load, I agree with you on that. And on another hand, using existing keywords helps to avoid

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

On Fri, Nov 20, 2015 at 4:00 PM, Alexey Shtokolov wrote: > Probably we should use another keyword for Fuel CI to prevent an extra > load on the infrastructure? For example "refuel" or smth like this? IMHO we should have ability to restart each one of two deployment

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Hi Stanislaw, The reason behind this is simple - deployment tests are heavy. Each deployment test occupies whole server for ~2 hours, for each commit we have 2 deployment tests (for current fuel-library master) and that’s just because we don’t test CentOS deployment for now. If we assume that

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Igor, it is much more clear for me now. Thank you :) On Fri, Nov 20, 2015 at 2:09 PM, Igor Belikov wrote: > Hi Stanislaw, > > The reason behind this is simple - deployment tests are heavy. Each > deployment test occupies whole server for ~2 hours, for each commit we have

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Hi Igor, would you be so kind tell, why fuel-library deployment tests doesn't support this? Maybe there is a link with previous talks about it? On Fri, Nov 20, 2015 at 1:34 PM, Igor Belikov wrote: > Hi, > > I’d like to inform you that all jobs running on Fuel CI (with

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Igor, Thank you for this feature. Afaiu recheck/reverify is mostly useful for internal CI-related fails. And Fuel CI and Openstack CI are two different infrastructures. So if smth is broken on Fuel CI, "recheck" will restart all jobs on Openstack CI too. And opposite case works the same way.

[openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Hi, I’d like to inform you that all jobs running on Fuel CI (with the exception of fuel-library deployment tests) now support retriggering via “recheck” or “reverify” comments in Gerrit. Exact regex is the same one used in Openstack-Infra’s zuul and can be found here

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Why not "recheck fuel" to align with how other OpenStack 3rd party CI hooks work? See: recheck xen-server or recheck hyper-v Best, -jay On 11/20/2015 05:24 AM, Igor Belikov wrote: Alexey, First of all, “refuel” sounds very cool. Thanks for raising this topic, I would like to hear more