<div dir="ltr">Hi Anita,<div><br></div><div>Sorry for the missunderstanding, I wasn't talking about populating the wiki pages.</div><div>I was talking about having zuul working seamlessly and meeting all the requirements, previous and new ones.</div>
<div>I am extremely grateful for your work on the CI systems, thank you so much, it wasn't intended any criticism to your work.</div><div><br></div><div>Best regards,</div><div>Lucas</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Aug 14, 2014 at 8:58 PM, Anita Kuno <span dir="ltr"><<a href="mailto:anteaya@anteaya.info" target="_blank">anteaya@anteaya.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 08/14/2014 12:50 PM, Lucas Eznarriaga wrote:<br>
> Hi,<br>
><br>
> Midokura CI should be up to date now too.<br>
> We have a problem with zuul-merger when the host id of <a href="http://review.openstack.org" target="_blank">review.openstack.org</a><br>
> changes. In this case, the new rsa key has to be added manually otherwise<br>
> the build will fail with a:<br>
><br>
> Merge Failed.<br>
><br>
> This change was unable to be automatically merged with the current state of<br>
> the repository. Please rebase your change and upload a new patchset<br>
><br>
> So if the <a href="http://review.openstack.org" target="_blank">review.openstack.org</a> host changes soon it will start failing<br>
> again.<br>
> That said, taking into account that August is the usual vacation month in<br>
> Europe and probably in some other parts as well, end of August sounds like<br>
> a tight deadline. Also, I have been attending to third-party meetings<br>
> regularly but the last one (I have checked the logs) and I feel like an<br>
> announcement for these new requirements should have been done there.<br>
><br>
> Have a great summer!<br>
><br>
> Lucas<br>
</div>Hi Lucas:<br>
<br>
Well this has been something I have been working on since summit and I<br>
hadn't expected the issue of naming to bog me down for three months, but<br>
it did. I'm grateful to Jim to have been able to address this issue and<br>
clear it up so well.<br>
<br>
Help me understand how creating a wikipage and populating it with<br>
contact information and editing the formatting for your comments will<br>
take more than 11 working days to accomplish. If it is really impossible<br>
for you to accomplish this work in this time and can demonstrate this to<br>
me, I will advocate on your behalf with the rest of the infra team. If<br>
you would like me to do this, I will need a deadline which you will hold<br>
yourself to.<br>
<br>
Thanks Lucas,<br>
Anita.<br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
><br>
> On Wed, Aug 13, 2014 at 8:23 PM, James E. Blair <<a href="mailto:corvus@inaugust.com">corvus@inaugust.com</a>> wrote:<br>
><br>
>> Hi,<br>
>><br>
>> We've updated the registration requirements for third-party CI systems<br>
>> here:<br>
>><br>
>> <a href="http://ci.openstack.org/third_party.html" target="_blank">http://ci.openstack.org/third_party.html</a><br>
>><br>
>> We now have 86 third-party CI systems registered and have undertaken an<br>
>> effort to make things more user-friendly for the developers who interact<br>
>> with them. There are two important changes to be aware of:<br>
>><br>
>> 1) We now generally name third-party systems in a descriptive manner<br>
>> including the company and product they are testing. We have renamed<br>
>> currently-operating CI systems to match these standards to the best of<br>
>> our abilities. Some of them ended up with particularly bad names (like<br>
>> "Unknown Function..."). If your system is one of these, please join us<br>
>> in #openstack-infra on Freenode to establish a more descriptive name.<br>
>><br>
>> 2) We have established a standard wiki page template to supply a<br>
>> description of the system, what is tested, and contact information for<br>
>> each system. See <a href="https://wiki.openstack.org/wiki/ThirdPartySystems" target="_blank">https://wiki.openstack.org/wiki/ThirdPartySystems</a> for<br>
>> an index of such pages and instructions for creating them. Each<br>
>> third-party CI system will have its own page in the wiki and it must<br>
>> include a link to that page in every comment that it leaves in Gerrit.<br>
>><br>
>> If you operate a third-party CI system, please ensure that you register<br>
>> a wiki page and update your system to link to it in every new Gerrit<br>
>> comment by the end of August. Beginning in September, we will disable<br>
>> systems that have not been updated.<br>
>><br>
>> Thanks,<br>
>><br>
>> Jim<br>
>><br>
>> _______________________________________________<br>
>> OpenStack-Infra mailing list<br>
>> <a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-Infra mailing list<br>
> <a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
><br>
<br>
<br>
_______________________________________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
</div></div></blockquote></div><br></div>