<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 29, 2018 at 10:09 AM Nigel Babu <<a href="mailto:nigelb@redhat.com">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This patch was merged today. </div></blockquote><div><br></div><div>Sorry, but what does "This" refer to?</div><div><br></div><div>Thanks - Michael<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We had some hiccups, but Humble and Madhu helped sort it out. I had one more hiccup where the encrypted key wasn't working and that's sorted out as well. All merges will now be auto-applied. Please re-base any existing patch before it can be merged.<br></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 12, 2018 at 10:39 PM John Strunk <<a href="mailto:jstrunk@redhat.com" target="_blank">jstrunk@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Overall, sounds good.</div>As a part of this, can we also add some documentation outlining these procedures and how this repo interacts w/ the ci system?<div><br></div><div>-John</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 12, 2018 at 3:22 AM Niels de Vos <<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Oct 12, 2018 at 10:59:08AM +0530, Nigel Babu wrote:<br>
> Hello folks,<br>
> <br>
> The centosci repo keeps falling behind in terms of reviews and merges +<br>
> delay in applying the merges on <a href="http://ci.centos.org" rel="noreferrer" target="_blank">ci.centos.org</a>. I'd like to propose the<br>
> following to change that. This change will impact everyone who runs a job<br>
> on Centos CI.<br>
> <br>
> * As soon as you merge a patch into that repo, we will apply that patch on<br>
> Centos CI using Jenkins/Travis (don't really care which one).<br>
> * Every team that has a job will have at least one committer (preferably<br>
> more than 1). Please feel free to review and merge patches as long as it<br>
> only applies to your job. If you want to add new committers.<br>
> * If you need to create a new job, you can ask us for initial review, but<br>
> the rest can be handled by your team independently.<br>
> * If you want an old job deleted, please file a bug.<br>
> <br>
> Does this sound acceptable? I'm going to deploy a CI job to apply master on<br>
> Centos CI on 29th. Please nominate folks from your teams who need explicit<br>
> commit access. The first day might be choppy in case there's a diff between<br>
> what's in <a href="http://ci.centos.org" rel="noreferrer" target="_blank">ci.centos.org</a> vs what's on the repo.<br>
<br>
Thanks! Having a job that automatically applies changes to the jobs in<br>
the CI will be very useful.<br>
<br>
Maybe we can have a MAINTAINERS or OWNERS file in the repo that lists<br>
who the contact for certain component tests is?<br>
<br>
Niels<br>
</blockquote></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_7853556751431160109gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</blockquote></div></div>