e5c03ea014
Do QA on current development branch
2013-10-17 09:44:33 -03:00
d5da29ea29
Don't force distribute in bootstrap, it's broken
2013-10-14 10:23:56 +01:00
83e72fe14d
A number of improvements to how we run builds on Travis
...
Among them:
* add Plone 4.0 and 4.1 under Python 2.6 to the testing matrix
* do not run Plone 4.3 with Python 2.6 and Plone 4.2 with Python 2.7 -- this
reduces the number of builds but keeps basically the same coverage
* only upload coverage info to Coveralls.io on one job per build, not on all
jobs
* upgrade zc.buildout to 1.7.1 (was 1.6.3)
* use Plone 4.3 by default (was 4.2)
2013-10-11 23:00:22 -03:00
ececd691bf
not needed?
2013-10-09 21:06:23 -03:00
e12a6c08b3
Use distribute on Travis CI
...
Travis has an old version of setuptools so we explicitly need to tell
bootstrap.py to use distribute.
2013-10-09 16:56:47 -03:00
a3c6447ee3
Use distribute on Travis CI
...
Travis has an old version of setuptools so we explicitly need to tell
bootstrap.py to use distribute.
2013-10-09 16:51:32 -03:00
95adaabb95
code coverage command now available
2013-10-06 14:17:24 -03:00
78370d222a
differentiate between global and matrix env variables
2013-10-06 13:31:57 -03:00
5fd312d520
add coveralls.io token
2013-10-06 13:21:48 -03:00
cf065ddde2
fix .travis.yml indentation
2013-10-05 20:16:08 -03:00
f9111f6dd6
add support for Coveralls.io
2013-10-05 20:03:06 -03:00
50d6ce63e6
make Travis IRC notification message to be one-line instead of three-lines
2013-10-05 12:29:55 -03:00
d98780971b
update to handling python versions in Makefile
2013-01-25 14:57:33 +01:00
0a3a9f44fd
we now officially support Plone 4.3
2013-01-24 23:00:52 +01:00
a871255f34
use Asko's buildout cache trick to speed up Travis builds
2013-01-24 17:46:02 +01:00
bbc8aa7b11
email notification committers not just myself
2013-01-24 14:29:13 +01:00
6fdacd0212
run tests also for Plone 4.3
2013-01-24 14:24:25 +01:00
61088cd2cb
Fixing something strange with rebase.
2012-10-14 14:16:23 -03:00
646f31b6cd
Fixing something strange with rebase.
2012-10-14 14:15:58 -03:00
51f9db529b
hmm, travis likes to have both `install` and `script`
2012-10-14 15:39:42 +02:00
10ba79ceb2
let's not use virtualenv on travis
...
it already provides its own virtual environment
2012-10-14 15:36:53 +02:00
c13b74d822
we should use the 'script' step in Travis instead of 'install'
2012-10-14 15:32:27 +02:00
992705ca46
run tests on python 2.6 as well
2012-10-14 13:10:52 +02:00
4ec9a62e23
use `make` for travis
2012-10-14 13:03:42 +02:00
395fd3bcee
support for Travis CI
2012-08-17 10:56:44 -03:00
hvelarde
Matthew Wilkes
Nejc Zupan
Fabiano Weimar dos Santos
Andreas Zeidler