Jenkins and unit-tests
by Pierre-Yves Chibon
Hi all,
Since there seemed to be agreement to put in place a CI server, I asked
Luke for some place on the Jenkins he uses.
So FedoraReview is now present over there:
http://jenkins.turbogears.org/job/FedoraReview/
Unfortunately, it seems that the unit-tests are not working properly.
Note: the server running the Jenkins is a RHEL, I guess 5 since python
2.4 is the default.
So to build against python 2.6, I use the following script copied from
other project built against 2.6 on this server:
rm -fr fedorareviewenv
virtualenv -p python2.6 --no-site-packages fedorareviewenv
source fedorareviewenv/bin/activate
easy_install coverage pylint pip
pip -q install git+git://github.com/cmheisel/nose-xcover.git
#python setup.py develop
nosetests --cover-erase --cover-package=src --with-xunit
--with-xcoverage
pylint -f parseable src | tee pylint.out
deactivate
Using ''python setup.py test'' does not improve things for the moment.
Additionally, we won't be able to have email notification for the
moment, it seems that they got more restrictive wrt how they send
emails.
On the 'plus' side, we have a nice integration of pylint :)
http://jenkins.turbogears.org/job/FedoraReview/violations/?
Finally, I set the build to be @daily but I can easily run it manually
if required.
Have a good evening,
Pierre
11 years, 6 months