Re: Plone 4.2 Experimental Jenkins job

On 4/12/12 5:32 PM, Timo Stollenwerk wrote:
> Am 10.04.2012 20:55, schrieb Eric Steele:
[..]
>> As a side note for everyone, we're now officially supporting both Python
>> 2.6 and 2.7. I'd like to run against both, if we could. Are we better
>> off with two separate jobs or as a single multi-configuration one?
>
> I think the quickest solution would be to just create an additional job
> for Python 2.7 for now. For the future I would like to look into a
> multi-configuration job setup, otherwise we will end up with a lot of jobs.


Not sure myself yet but maybe this comes in handy?

http://blog.shiningpanda.com/2011/11/python-multiple-versions-testing-with.html

Raphael

>
> What about Jenkins jobs for Plone 4.3? I could use them as a playground
> to test new job configurations as long as 4.2 is not out of the door.
>
> Cheers,
> timo
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Plone-website mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-website
> The Wiki: http://plone.org/development/current/projects/WebsiteTeam
>



------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam