Repositories for oVirt Node Automated Testing

[Itamar Heim]

On 06/21/2012 08:24 PM, Mike Burns wrote:
> On Thu, 2012-06-21 at 12:32 -0400, Robert Middleswarth wrote:
>> Is it going to be managed though gerrit?  Or are you looking for
>> something simpler?  If simpler the maybe gitolite is an good choice?  I
>> use it in my day job.  From what I have read there is no option other
>> then a custom hook to limit write access to folders a git limitation not
>> gitolite limitation but you can limit it by branches.
>
> Most likely through gerrit.  And the gerrit interface does support
> restrictions based on branch, though I don't like the branch-by-branch
> approach.  I'd still prefer separate repos for separate projects.
>
> Mike
>>
>> Thanks
>> Robert
>>
>> On 06/21/2012 12:08 PM, Mike Burns wrote:
>>> On Thu, 2012-06-21 at 17:47 +0200, Fabian Deutsch wrote:
>>>> Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
>>>>> ----- Original Message -----
>>>>>> From: "Fabian Deutsch"<fabiand at redhat.com>
>>>>>> To: infra at ovirt.org
>>>>>> Sent: Thursday, June 21, 2012 6:42:46 PM
>>>>>> Subject: Repositories for oVirt Node Automated Testing
>>>>>>
>>>>>> Hey,
>>>>>>
>>>>>> I'm working on bringing automated testing to oVirt Node.
>>>>>>
>>>>>> The current code is hosted at [1], but it would be nice if I could
>>>>>> host
>>>>>> at least the ovirt specific client and the ovirt specififc testsuites
>>>>>> on
>>>>>> the ovirt infrastructure.
>>>>>>
>>>>>> Is there anything specififc for me to do, besides asking for these
>>>>>> repos?
>>>>> I assume we need a git repo for all automated testing in jenkins.
>>>>>
>>>>> i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ).
>>>>> another option is to have a separate branch for each project..
>>>>>
>>>>> thoughts?
>>>> I'd be happy with the one-subdir-per-subproject approach, but I wouldn't
>>>> go with the branch solution.
>>> Problem with having 1 repo for all projects is ownership.  Who can
>>> commit changes to the repo.  Do we have a long list of committers?  Do
>>> we have a limited list?  Also, there is the fact that I might be testing
>>> only engine and don't want anything from node or vdsm.  We already have
>>> a ovirt-engine-sdk-tests repo.  I think we should continue along those
>>> lines with a separate ovirt-node-tests repo, vdsm-tests repo, etc...

+1 to using gerrit
+1 to repo by project

unless any objections, I'll create this repo next week for fabian as a 
sub repo as part of the ovirt node project