<div dir="ltr"><div><div><div>Matthew,<br><br></div>It's great that we have this test. But why to rerun it for no changes?<br>It was executed only when a new patch was published for CR or CR was rebased.<br></div>Now it is executed on "fuel:recheck".<br><br></div>Agree, adding a plugin would be helpful.<br><br><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Aleksey Kasatkin
<br><br></div></div></div>
<br><div class="gmail_quote">On Fri, Apr 22, 2016 at 4:19 PM, Matthew Mosesohn <span dir="ltr"><<a href="mailto:mmosesohn@mirantis.com" target="_blank">mmosesohn@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Aleksey, actually I want to extend the test group we run there. Many<br>
changes coming out of nailgun are actually creating BVT failures that<br>
can only be prevented by such tests. One such extension would be<br>
adding a plugin to the deployment to ensure that basic plugins are<br>
still deployable.<br>
<br>
I'm ok with tweaking recheck flags, but we should not try to avoid<br>
using the CI that saves us from regressions.<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Apr 22, 2016 at 3:43 PM, Aleksey Kasatkin<br>
<<a href="mailto:akasatkin@mirantis.com">akasatkin@mirantis.com</a>> wrote:<br>
> Hi Dmitry,<br>
><br>
> Thank you for update.<br>
> Is it intended that master.fuel-web.pkgs.ubuntu.review_fuel_web_deploy job<br>
> for code requests to fuel-web runs at every recheck now?<br>
> Before the change it was executed for new patch/rebase only.<br>
> Its run takes about 1.5 hour and there is little sense to run it more than<br>
> once for the same patch.<br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> Aleksey Kasatkin<br>
><br>
><br>
> On Fri, Apr 22, 2016 at 10:59 AM, Dmitry Kaiharodsev<br>
> <<a href="mailto:dkaiharodsev@mirantis.com">dkaiharodsev@mirantis.com</a>> wrote:<br>
>><br>
>> Hi to all,<br>
>><br>
>> please be informed that recently we've merged a patch[0]<br>
>> that allow to re-trigger fuel-ci[1] tests by commenting review with<br>
>> keywords "fuel: recheck"[2]<br>
>><br>
>> For now actual list of Jenkins jobs with retrigger by "fuel: recheck"[2]<br>
>> keyword looks like:<br>
>><br>
>> 7.0.verify-python-fuelclient<br>
>> 8.0.fuel-library.pkgs.ubuntu.neutron_vlan_ha<br>
>> 8.0.fuel-library.pkgs.ubuntu.smoke_neutron<br>
>> 8.0.verify-docker-fuel-web-ui<br>
>> 8.0.verify-fuel-web<br>
>> 8.0.verify-fuel-web-ui<br>
>> fuellib_noop_tests<br>
>> master.fuel-agent.pkgs.ubuntu.review_fuel_agent_one_node_provision<br>
>> master.fuel-astute.pkgs.ubuntu.review_astute_patched<br>
>> master.fuel-library.pkgs.ubuntu.neutron_vlan_ha<br>
>> master.fuel-library.pkgs.ubuntu.smoke_neutron<br>
>> master.fuel-ostf.pkgs.ubuntu.gate_ostf_update<br>
>> master.fuel-web.pkgs.ubuntu.review_fuel_web_deploy<br>
>> master.python-fuelclient.pkgs.ubuntu.review_fuel_client<br>
>> mitaka.fuel-agent.pkgs.ubuntu.review_fuel_agent_one_node_provision<br>
>> mitaka.fuel-astute.pkgs.ubuntu.review_astute_patched<br>
>> mitaka.fuel-library.pkgs.ubuntu.neutron_vlan_ha<br>
>> mitaka.fuel-library.pkgs.ubuntu.smoke_neutron<br>
>> mitaka.fuel-ostf.pkgs.ubuntu.gate_ostf_update<br>
>> mitaka.fuel-web.pkgs.ubuntu.review_fuel_web_deploy<br>
>> mitaka.python-fuelclient.pkgs.ubuntu.review_fuel_client<br>
>> old.verify-nailgun_performance_tests<br>
>> verify-fuel-astute<br>
>> verify-fuel-devops<br>
>> verify-fuel-docs<br>
>> verify-fuel-library-bats-tests<br>
>> verify-fuel-library-puppetfile<br>
>> verify-fuel-library-python<br>
>> verify-fuel-library-tasks<br>
>> verify-fuel-nailgun-agent<br>
>> verify-fuel-plugins<br>
>> verify-fuel-qa-docs<br>
>> verify-fuel-stats<br>
>> verify-fuel-ui-on-fuel-web<br>
>> verify-fuel-web-docs<br>
>> verify-fuel-web-on-fuel-ui<br>
>> verify-nailgun_performance_tests<br>
>> verify-puppet-modules.lint<br>
>> verify-puppet-modules.syntax<br>
>> verify-puppet-modules.unit<br>
>> verify-python-fuelclient<br>
>> verify-python-fuelclient-on-fuel-web<br>
>> verify-sandbox<br>
>><br>
>><br>
>> [0] <a href="https://review.fuel-infra.org/#/c/17916/" rel="noreferrer" target="_blank">https://review.fuel-infra.org/#/c/17916/</a><br>
>> [1] <a href="https://ci.fuel-infra.org/" rel="noreferrer" target="_blank">https://ci.fuel-infra.org/</a><br>
>> [2] without quotes<br>
>> --<br>
>> Kind Regards,<br>
>> Dmitry Kaigarodtsev<br>
>> Mirantis, Inc.<br>
>><br>
>> <a href="tel:%2B38%20%28093%29%20522-09-79" value="+380935220979">+38 (093) 522-09-79</a> (mobile)<br>
>> <a href="tel:%2B38%20%28057%29%20728-4214" value="+380577284214">+38 (057) 728-4214</a> (office)<br>
>> Skype: d1mas85<br>
>><br>
>> 38, Lenin avenue<br>
>> Kharkov, Ukraine<br>
>> <a href="http://www.mirantis.com" rel="noreferrer" target="_blank">www.mirantis.com</a><br>
>> <a href="http://www.mirantis.ru" rel="noreferrer" target="_blank">www.mirantis.ru</a><br>
>> <a href="mailto:dkaiharodsev@mirantis.com">dkaiharodsev@mirantis.com</a><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>