If you limit yourself to only testing once jenkins has put a +1 on,
then you can down a bit... Not sure how to build that into Jay Pipe's
pipeline though

On 13 August 2014 10:30, Asselin, Ramy <ramy.asse...@hp.com> wrote:
> I remember infra team objected to the nightly builds. They wanted reports on 
> every patch set in order to report to gerrit.
> In the short-term, I suggest you test on every patch set, but limit the 
> resources. This will cause 'long delays' but jobs will eventually go through.
> In the long-term, you'll need to scale.
> Currently, we're just running 1 job per back-end at a time.
>
> -----Original Message-----
> From: David Pineau [mailto:dav.pin...@gmail.com]
> Sent: Wednesday, August 13, 2014 2:19 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
>
> Hello,
>
> I have currently setup the Scality CI not to report (mostly because it isn't 
> fully functionnal yet, as the machine it runs on turns out to be undersized 
> and thus the tests fails on some timeout), partly because it's currently a 
> nightly build. I have no way of testing multiple patchsets at the same time 
> so it is easier this way.
>
> How do you plan to "Officialize" the different 3rd party CIs ? I remember 
> that the cinder meeting about that in the Atlanta Summit concluded that a 
> nightly build would be enough, but such build cannot really report on gerrit.
>
> David Pineau
> gerrit: Joachim
> IRC#freenode: joa
>
> 2014-08-13 2:28 GMT+02:00 Asselin, Ramy <ramy.asse...@hp.com>:
>> I forked jaypipe’s repos & working on extending it to support
>> nodepool, log server, etc.
>>
>> Still WIP but generally working.
>>
>>
>>
>> If you need help, ping me on IRC #openstack-cinder (asselin)
>>
>>
>>
>> Ramy
>>
>>
>>
>> From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com]
>> Sent: Monday, August 11, 2014 11:33 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI
>> systems
>>
>>
>>
>> On 12 August 2014 07:26, Amit Das <amit....@cloudbyte.com> wrote:
>>
>> I would like some guidance in this regards in form of some links, wiki
>> pages etc.
>>
>>
>>
>> I am currently gathering the "driver cert test results" i.e. tempest
>> tests from devstack in our environment & CI setup would be my next step.
>>
>>
>>
>> This should get you started:
>>
>> http://ci.openstack.org/third_party.html
>>
>>
>>
>> Then Jay Pipes' excellent two part series will help you with the
>> details of getting it done:
>>
>> http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing
>> -system/
>>
>> http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing
>> -system-part-2/
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> David Pineau,
> Developer R&D at Scality
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Duncan Thomas

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to