"Pretty" Continuous Integration for Python

Question

This is a slightly.. vain question, but BuildBot's output isn't particularly nice to look at..

For example, compared to..

• phpUnderControl
• Hudson
• CruiseControl.rb

..and others, BuildBot looks rather.. archaic

I'm currently playing with Hudson, but it is very Java-centric (although with this guide, I found it easier to setup than BuildBot, and produced more info)

Basically: is there any Continuous Integration systems aimed at python, that produce lots of shiney graphs and the likes?

---

Update: After trying a few alternatives, I think I'll stick with Hudson. Integrity was nice and simple, but quite limited. I think Buildbot is better suited to having numerous build-slaves, rather than everything running on a single machine like I was using it.

Setting Hudson up for a Python project was pretty simple:

• Download Hudson from https://hudson.dev.java.net/
• Run it with java -jar hudson.war
• Open the web interface on the default address of http://localhost:8080
• Go to Manage Hudson, Plugins, click "Update" or similar
• Install the Git plugin (I had to set the git path in the Hudson global preferences)
• Create a new project, enter the repository, SCM polling intervals and so on
• Install nosetests via easy_install if it's not already
• In the a build step, add nosetests --with-xunit --verbose
• Check "Publish JUnit test result report" and set "Test report XMLs" to **/nosetests.xml

That's all that's required. You can setup email notifications, and the plugins are worth a look. A few I'm currently using for Python projects:

• SLOCCount plugin to count lines of code (and graph it!) - you need to install sloccount separately
• Violations to parse the PyLint output (you can setup warning thresholds, graph the number of violations over each build)
• Cobertura can parse the coverage.py output. Nosetest can gather coverage while running your tests, using nosetests --with-coverage (this writes the output to **/coverage.xml)

Answer 1

Don't know if it would do : Bitten is made by the guys who write Trac and is integrated with Trac. Apache Gump is the CI tool used by Apache. It is written in Python.

Answer 2

We've had great success with TeamCity as our CI server and using nose as our test runner. Teamcity plugin for nosetests gives you count pass/fail, readable display for failed test( that can be E-Mailed). You can even see details of the test failures while you stack is running.

If of course supports things like running on multiple machines, and it's much simpler to setup and maintain than buildbot.

Answer 3

You might want to check out Nose and NoseXUnit. You can have it run pylint, your unit tests, and coverage checks with this command:

nosetests --with-nosexunit --enable-audit --enable-cover

That'll be helpful if you want to go the Hudson route or if you want to use another CI server that has support for JUnit test reporting.

(And yes, you realize how regrettable a name NoseXUnit is when you see it in all-lowercase :-/ )

Answer 4

Buildbot's waterfall page can be considerably prettified. Here's a nice example http://build.chromium.org/buildbot/waterfall/waterfall

Answer 5

We have used bitten quite a bit. It is pretty and integrates well with Trac, but it is a pain in the butt to customize if you have any nonstandard workflow. Also there just aren't as many plugins as there are for the more popular tools. Currently we are evaluating Hudson as a replacement.

Answer 6

Signal is another option. You can know more about it and watch a video also here.