On 3/27/13 7:33 AM, Héctor Velarde wrote:
yesterday I successfully started testing various add ons against
different versions of Plone and Python using Travis CI and our good
old testing configurations in buildout.plonetest.
you can see some nice examples in:
https://travis-ci.org/collective/collective.prettydate
https://travis-ci.org/collective/plone.app.imagecropping
ideas were shamelessly "stolen" from plone.api and everything is
documented in:
https://github.com/collective/buildout.plonetest#testing-in-travis-ci-with-multiple-versions-of-plone
now I'm facing a new problem that could be interesting for others: I
want to test some Dexterity-based content types on Plone 4.1 but I
would need to add the KGS to the plone-4.1.x.cfg configuration:
[buildout]
extends =
http://dist.plone.org/release/4.1-latest/versions.cfg
https://good-py.appspot.com/release/dexterity/1.2.1 <-- this one!
...
anybody against this?
I would probably make a separate plonetest configuration for Plone 4.1 +
Dexterity. Plone 4.1 didn't officially include Dexterity, and pretending
it did could cause someone to draw the wrong conclusions from their test
runs.
Also, that's not the right way to extend Dexterity versions; you should do:
extends =
https://good-py.appspot.com/release/dexterity/1.2.1?plone=4.1.6
That's because the Dexterity 1.2.1 KGS contains a couple different
versions of five.grok for compatibility with different versions of
Zope2. If you specify the plone version as a parameter like this it has
enough info to constrain it to the correct version; without it it'll
just include the latest one that's in the KGS which might not be correct.
David
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
