Re: Plone 4.2 Experimental Jenkins job
Timo Stollenwerk <[email protected]> Tue, 17 Apr 2012 10:49:33 +0200
| Newsgroups | gmane.comp.web.zope.plone.website |
|---|---|
| Message-ID | <[email protected]> |
Am 17.04.2012 10:41, schrieb Raphael Ritz: > 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 Yes. I already looked into that. Could be an option. We have to figure out if this plugin plays well with our job architecture and the other plugins we have. Cheers, timo ------------------------------------------------------------------------------ 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