Fork me on GitHub

dominicrodger.com

Travis, You Are Awesome

I came across Travis CI this week, and it's awesome.

I've got a bunch of tests for django-magazine, but I'm not very good at running them. It turns out that unit tests aren't very useful if you don't run them, so I wanted to make sure that every time I pushed code to it, the tests run. Enter Travis CI.

Easy Unit Testing for Reusable Apps

django-magazine is a reusable app - that is, it doesn't ship with settings files, so you can't run its tests just after installing it¹.

I wasn't sure what the easiest way to handle this was, so I looked around for Django reusable apps that were already using Travis, and stumbled across django-forms-builder. They'd solved this by adding an example_project folder, which had a simple settings file, a urls file and a manage.py².

That allows me to run the tests without any extra set-up, though I still haven't worked out how to allow people who've just installed from pip³ to run the tests right out of the box.

.travis.yml

There are just two things you need to do to get Travis CI working for your project.

Firstly - sign in on their website. There's a slightly scary message about giving it write access to your repositories, but there's a decent enough reason on the Travis site explaining why they need it⁴.

Secondly - add a .travis.yml file to your root directory, commit, and push to GitHub. Travis CI will pick up your change, and start building. My file currently looks like this:

language: python
python:
  - "2.6"
  - "2.7"
env:
  - DJANGO=1.3.1
  - DJANGO=1.4
install:
  - pip install -q Django==$DJANGO --use-mirrors
  - pip install -r requirements.txt --use-mirrors
  - pip install pep8
script:
  - pep8 --exclude=migrations magazine
  - ./magazine/example_project/manage.py test magazine

This will kick off four builds:

Python 2.6 and Django 1.3.1;
Python 2.6 and Django 1.4;
Python 2.7 and Django 1.3.1;
Python 2.7 and Django 1.4.

Each of those will run in parallel, and you'll then get an e-mail with the status of your build, if it changed (pleasingly, it doesn't e-mail you for every build - only if the status of it has switched between fixed and broken). Go take a look at an example build result.

The --use-mirrors stuff is an attempt to help Travis CI avoid overloading PyPI.

Bonus Points: PEP-8

I've recently discovered PEP-8, which I half knew about, but I'd never attempted to make my code meet it. Then someone forked django-magazine to make it meet PEP-8, and I was shamed into fixing it. I've added a line to my .travis.yml file so the build fails if checked-in code is not PEP-8 friendly.

Advertise Your Status

Travis CI even provides an image that'll show your current build status - adding it to my README.md file allows me to advertise that (and implicitly, that I'm a bit obsessive) using:

https://secure.travis-ci.org/dominicrodger/django-magazine.png?branch=master

Currently, that looks like:

All this is to say, Travis CI is awesome, and you should use it.

This is probably a good time to point out that django-magazine is not available on PyPI yet. I've never added anything to PyPI before, and there's a couple of things I'd like to sort out before doing that. Firstly I'd like to make sure I've tagged things properly, and secondly I need to factor out the book review stuff which is currently not tested, and is very specific to my particular use case. ↩
They all had a templates folder, with a base template, which django-magazine doesn't need. That might be because I've done something wrong (every template extends
magazine/magazine_base.html, which doesn't have much in the way of HTML, but enough that all the tests pass, one of these days I should probably give it some simple styles). ↩
As opposed to git clone, which is what Travis CI does, which means that the example_project code is in a predictable location (also, I've not yet added example_project to my manifest file, so it's not installed by pip). ↩
"Travis CI needs write access for setting up service hooks for your repositories when you request it, but it won't touch anything else." — Getting Started - Travis CI Documentation

I'd love there to be a workaround for this, but Travis is awesome enough that I mostly just don't care. ↩

Other articles

I Know Nothing

Friday 20 April 2012
By Dominic Rodger

In code.

See, I know nothing! — Manuel

I distinctly remember being 17 years old, I'd just finished re-launching a site for a charity I was involved with¹, and I confidently declared that I knew all there was to know about building websites. And I believed it.

At the time, I ...
read more
Getting Better at Testing

Thursday 12 April 2012
By Dominic Rodger

In code.

I started with unit testing about 4 years ago. I started writing what were probably integration tests, when I was working on the database backend of our application. The tests I wrote were designed to make sure that our process which saved data actually saved data. Saving data involved creating ...
read more
Starting with Pelican

Saturday 07 April 2012
By Dominic Rodger

In code.

A brief history of my (failed) blogs

In about 1998, I was building a website for a friend. The site was entirely static. I'd already learned the hard way about the pain of trying to keep lots of separate static HTML files visually consistent.

To build the site, I ...
read more
Starting Over

Saturday 07 April 2012
By Dominic Rodger

In code.

Please sir, can I start again?

Every once in a while, I want to start again.

I currently have 6 different sites using Kaléo¹. The code is stored in a private git repository, and synced out to 6 different places every time I need to make a change ...
read more
Test-Driven Development with Django & South

Tuesday 11 January 2011
By Dominic Rodger

In code.

I'd basically given up on attempting test-driven with Django, given the project I'm currently working on uses models with a lot of South migrations. Just building the database and running the migrations could take a minute or so when running manage.py test, and resetting the database to ...
read more