<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 20, 2017 at 2:51 PM, Emilien Macchi <span dir="ltr"><<a href="mailto:emilien@redhat.com" target="_blank">emilien@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Jun 20, 2017 at 12:49 PM, Wesley Hayutin <<a href="mailto:whayutin@redhat.com">whayutin@redhat.com</a>> wrote:<br>
> Greetings,<br>
><br>
> It's become apparent that everyone in the tripleo community may not be aware<br>
> of where CI specific work is tracked.<br>
><br>
> To find out which CI related features or bug fixes are in progress or to see<br>
> the backlog please consult [1].<br>
><br>
> To find out what issues have been found in OpenStack via CI please consult<br>
> [2].<br>
><br>
> Thanks!<br>
<br>
</span>Thanks Wes for these informations. I was about to start adding more<br>
links and informations when I realized monitoring TripleO CI might<br>
deserve a little bit of training and documentation.<br>
I'll take some time this week to create a new section in TripleO docs<br>
with useful informations that we can easily share with our community<br>
so everyone can learn how to be aware about CI status.<br>
<span class=""><br></span></blockquote><div><br></div><div>Emilien,</div><div>That's a really good point, we should have this information in doc.</div><div>You are a busy guy, we'll take care of that.</div><div><br></div><div>Thanks for the input!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
><br>
> [1] <a href="https://trello.com/b/U1ITy0cu/tripleo-ci-squad" rel="noreferrer" target="_blank">https://trello.com/b/U1ITy0cu/<wbr>tripleo-ci-squad</a><br>
> [2] <a href="https://trello.com/b/WXJTwsuU/tripleo-and-rdo-ci-status" rel="noreferrer" target="_blank">https://trello.com/b/WXJTwsuU/<wbr>tripleo-and-rdo-ci-status</a><br>
><br>
</span>> ______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Emilien Macchi<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>