Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

2016-04-22 Thread Aleksey Kasatkin
Matthew, It's great that we have this test. But why to rerun it for no changes? It was executed only when a new patch was published for CR or CR was rebased. Now it is executed on "fuel:recheck". Agree, adding a plugin would be helpful. Aleksey Kasatkin On Fri, Apr 22, 2016 at 4:19 PM,

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

2016-04-22 Thread Matthew Mosesohn
Aleksey, actually I want to extend the test group we run there. Many changes coming out of nailgun are actually creating BVT failures that can only be prevented by such tests. One such extension would be adding a plugin to the deployment to ensure that basic plugins are still deployable. I'm ok

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

2016-04-22 Thread Aleksey Kasatkin
Hi Dmitry, Thank you for update. Is it intended that master.fuel-web.pkgs.ubuntu.review_fuel_web_deploy job for code requests to fuel-web runs at every recheck now? Before the change it was executed for new

[openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

2016-04-22 Thread Dmitry Kaiharodsev
Hi to all, please be informed that recently we've merged a patch[0] that allow to re-trigger fuel-ci[1] tests by commenting review with keywords "fuel: recheck"[2] For now actual list of Jenkins jobs with retrigger by "fuel: recheck"[2] keyword looks like: 7.0.verify-python-fuelclient