
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Alexey,<div class=""><br class=""></div><div class="">First of all, “refuel” sounds very cool.</div><div class="">Thanks for raising this topic, I would like to hear more opinions here.</div><div class="">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 confusion and provides expected behaviour for our CI jobs. Far too many times I’ve heard questions like “Why ‘recheck’ doesn’t retrigger Fuel CI jobs?”.</div><div class=""><br class=""></div><div class="">So I would like to hear more thoughts here from our developers. And I will investigate how another third party CI systems handle this questions.<br class=""><div class="">

<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">--</div><div class="">Igor Belikov</div><div class="">Fuel CI Engineer</div><div class=""><a href="mailto:ibelikov@mirantis.com" class="">ibelikov@mirantis.com</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">

</div>

<br class=""><div><blockquote type="cite" class=""><div class="">On 20 Nov 2015, at 16:00, Alexey Shtokolov <<a href="mailto:ashtokolov@mirantis.com" class="">ashtokolov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class="">Igor,<br class=""><br class=""></div>Thank you for this feature.<br class="">Afaiu recheck/reverify is mostly useful for internal CI-related fails. And Fuel CI and Openstack CI are two different infrastructures. <br class="">So if smth is broken on Fuel CI, "recheck" will restart all jobs on Openstack CI too. And opposite case works the same way.<br class=""></div><br class=""></div>Probably we should use another keyword for Fuel CI to prevent an extra load on the infrastructure? For example "refuel" or smth like this?<br class=""><br class=""></div>Best regards, <br class=""></div>Alexey Shtokolov<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2015-11-20 14:24 GMT+03:00 Stanislaw Bogatkin <span dir="ltr" class=""><<a href="mailto:sbogatkin@mirantis.com" target="_blank" class="">sbogatkin@mirantis.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Igor,<div class=""><br class=""></div><div class="">it is much more clear for me now. Thank you :)</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Nov 20, 2015 at 2:09 PM, Igor Belikov <span dir="ltr" class=""><<a href="mailto:ibelikov@mirantis.com" target="_blank" class="">ibelikov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi Stanislaw,<div class=""><br class=""></div><div class="">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.</div><div class="">If we assume that developers will rertrigger deployment tests only when retrigger would actually solve the failure - it’s still not smart in terms of HW usage to retrigger both tests when only one has failed, for example.</div><div class="">And there are cases when retrigger just won’t do it and CI Engineer must manually erase the existing environment on slave or fix it by other means, so it’s better when CI Engineer looks through logs before each retrigger of deployment test.</div><div class=""><br class=""></div><div class="">Hope this answers your question.</div><div class=""><span class=""><br class=""><div class="">

<div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class=""><div class="">--</div><div class="">Igor Belikov</div><div class="">Fuel CI Engineer</div><div class=""><a href="mailto:ibelikov@mirantis.com" target="_blank" class="">ibelikov@mirantis.com</a></div><div class=""><br class=""></div></div></div></div></div></span><div class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On 20 Nov 2015, at 13:57, Stanislaw Bogatkin <<a href="mailto:sbogatkin@mirantis.com" target="_blank" class="">sbogatkin@mirantis.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">Hi Igor,<div class=""><br class=""></div><div class="">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?</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Nov 20, 2015 at 1:34 PM, Igor Belikov <span dir="ltr" class=""><<a href="mailto:ibelikov@mirantis.com" target="_blank" class="">ibelikov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi,<div class=""><br class=""></div><div class="">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.</div><div class="">Exact regex is the same one used in Openstack-Infra’s zuul and can be found here <a href="https://github.com/fuel-infra/jenkins-jobs/blob/master/servers/fuel-ci/global.yaml#L3" target="_blank" class="">https://github.com/fuel-infra/jenkins-jobs/blob/master/servers/fuel-ci/global.yaml#L3</a></div><div class=""><br class=""></div><div class="">CI-Team kindly asks you to not abuse this option, unfortunately not every failure could be solved by retriggering.</div><div class="">And, to stress this out once again: fuel-library deployment tests don’t support this, so you still have to ask for a retrigger in #fuel-infra irc channel.</div><div class=""><br class=""></div><div class="">Thanks for attention.<br class=""><div class="">

<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word" class=""><div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word" class=""><div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word" class=""><div class="">--</div><div class="">Igor Belikov</div><div class="">Fuel CI Engineer</div><div class=""><a href="mailto:ibelikov@mirantis.com" target="_blank" class="">ibelikov@mirantis.com</a></div><div class=""><br class=""></div></div><br class=""></div><br class=""></div><br class=""><br class="">

</div>

<br class=""></div></div><br class="">__________________________________________________________________________<br class="">

OpenStack Development Mailing List (not for usage questions)<br class="">

Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">

<br class=""></blockquote></div><br class=""></div>

__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></div><br class="">__________________________________________________________________________<br class="">

OpenStack Development Mailing List (not for usage questions)<br class="">

Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">

<br class=""></blockquote></div><br class=""></div>

</div></div><br class="">__________________________________________________________________________<br class="">

OpenStack Development Mailing List (not for usage questions)<br class="">

Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">

<br class=""></blockquote></div><br class=""><br clear="all" class=""><br class="">-- <br class=""><div class="gmail_signature"><div dir="ltr" class="">---<div class="">WBR, Alexey Shtokolov</div></div></div>

</div>

__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>