[Gluster-infra] Maintaining gluster/centosci repo

[Michael Adam]

On Mon, Oct 29, 2018 at 10:09 AM Nigel Babu <nigelb at redhat.com> wrote:

> This patch was merged today.
>

Sorry, but what does "This" refer to?

Thanks - Michael


> 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.
>
> On Fri, Oct 12, 2018 at 10:39 PM John Strunk <jstrunk at redhat.com> wrote:
>
>> Overall, sounds good.
>> As a part of this, can we also add some documentation outlining these
>> procedures and how this repo interacts w/ the ci system?
>>
>> -John
>>
>> On Fri, Oct 12, 2018 at 3:22 AM Niels de Vos <ndevos at redhat.com> wrote:
>>
>>> On Fri, Oct 12, 2018 at 10:59:08AM +0530, Nigel Babu wrote:
>>> > Hello folks,
>>> >
>>> > The centosci repo keeps falling behind in terms of reviews and merges +
>>> > delay in applying the merges on ci.centos.org. I'd like to propose the
>>> > following to change that. This change will impact everyone who runs a
>>> job
>>> > on Centos CI.
>>> >
>>> > * As soon as you merge a patch into that repo, we will apply that
>>> patch on
>>> > Centos CI using Jenkins/Travis (don't really care which one).
>>> > * Every team that has a job will have at least one committer
>>> (preferably
>>> > more than 1). Please feel free to review and merge patches as long as
>>> it
>>> > only applies to your job. If you want to add new committers.
>>> > * If you need to create a new job, you can ask us for initial review,
>>> but
>>> > the rest can be handled by your team independently.
>>> > * If you want an old job deleted, please file a bug.
>>> >
>>> > Does this sound acceptable? I'm going to deploy a CI job to apply
>>> master on
>>> > Centos CI on 29th. Please nominate folks from your teams who need
>>> explicit
>>> > commit access. The first day might be choppy in case there's a diff
>>> between
>>> > what's in ci.centos.org vs what's on the repo.
>>>
>>> Thanks! Having a job that automatically applies changes to the jobs in
>>> the CI will be very useful.
>>>
>>> Maybe we can have a MAINTAINERS or OWNERS file in the repo that lists
>>> who the contact for certain component tests is?
>>>
>>> Niels
>>>
>>
>
> --
> nigelb
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-infra/attachments/20181029/b3dc43bd/attachment.html>