When a job has finished, fetch the log.

(Fetching the log of an on-going build makes caching kinda pointless, so we'll just ignore logs of unfinished jobs)

• add useful info to base template (e.g. link to source, site name, etc.)
• bootstrap
• JS sugar, e.g. use JS to skip repo-redirect

List recent builds in repo view as well as latest build.

Places where we should link externally:

• builds (travis build and github compare)
• jobs (travis job)
• repository (github)

Simple unit tests for views and context processor.

Should list overall build status and individual job statuses. A link to the github "compare" URL would be handy too.

We should cache as much as possible to avoid overloading the Travis servers.

In the short term this means using Django's cache with a smallish (e.g. 300 seconds) TTL.

In the long term I'd like to store API responses more permanently once they have finished (i.e. the data is now immutable and won't go stale).

TravisPy has its own internal cache, we might be able to hook into that.