Re: Porting tests to plone.app.testing and removal of legacy packages

Am 28.01.2015 um 11:15 schrieb Patrick Gerken:
> On 28.01 10:06, Jens W. Klein wrote:
>> On 2015-01-28 09:50, Ramon Navarro Bosch wrote:
>>> I'm agree with Timo, we should try to be carefull. Our use case is much
>>> different to one repo projects where everybody works on pull requests so
>>> we need to try to follow the rules we agreed.
>>>
>>> Maybe we need to define a better process for testing plip so we can
>>> ensure that we have a jenkins job equal to real jenkins job. On the
>>
>> +1000
>> this plus a check if every checkout is uptodate with target branch (most 
>> of the time master) of the packages.
> 
> I'd like to point to this:
> https://github.com/fschulze/mr.developer/commit/b76e77ffb8ccfd8a7accf329f465d589179b554c
> 
> There is no release of mr.developer yet, so the bug that changing
> branches on update might hurt us still on jenkins.

I don't think this is relevant since we are doing a fresh checkout for
every single build.

Cheers,
Timo

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/