On 2012-10-12 14:32:44 +0000, Tom Gross said:
There is no automated way. But adding a buildout based on one of these
http://svn.plone.org/svn/collective/buildout/plonetest/
(any reason to not have these on github?)
I am interested in moving them to github (and leaving the old ones in
place with a note) but IIRC davisagli and I didn't agree on what to
call them. I don't like "plonetest" because that is meaningless AFAICT
(or at least, I don't understand what it means. Buildouts for… testing?)
So, we can either call them:
- buildout.plonetest
And I'll forfeit my opinion, or we can come up with a better name e.g.:
- buildout.plone?
and adding .travis.yml file *IS* easy and quick ;)
language: python
python:
- 2.7
install:
- python bootstrap.py
- bin/buildout
script:
- bin/test
This should be added to ZopeSkel IMO.
Cool, thanks for the refresher. You mean templer :-)
Alex
:Tom
On 12.10.12 16:03, Alex Clark wrote:
On 2012-10-12 11:46:17 +0000, Tom Gross said:
Done. I also added a travis CI hook :)
w00t. Do we have easy travis-ci-ability in GitHub Collective yet?
:Tom
On 12.10.12 11:39, Jean-Michel FRANCOIS wrote:
Hi,
Could someone release this addon. Last commits fixes an issue for Plone
4.2 and move to github.
Regards / Cordialement,
JeanMichel FRANCOIS
Find me on Twitter <http://twitter.com/toutpt> / Retrouvez moi sur
Twitter <http://twitter.com/toutpt_nantes>
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
--
Alex Clark · https://www.gittip.com/aclark4life/
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
