Tracking development consistency
June 18, 2008 – 23:35Rationale
Our small team has 3 developers working full time on various projects. We practice throughout automated testing and aim to get 100% code coverage with unit tests.
Our internal version control system is git. Active development within git means couple or more new branches in the central repo daily and lots of merges.
Someone has to keep an eye on this whole stuff.
Having lots of automated tests, makes it much easier than running QC on them mannually after every commit 
Questions to be answererd:
- is the last push ok?
- is the last merge to the master ok?
- is this new branch ok?
Solution
We use buildbot.
It has to watch several things:
- Commits to the master branch, which are usually pre-release merges for my review.
- Commits to other branches, which are usually work-in-progress
- New branches – new work is done or something tangible appeared
Nice to have
Some integration with Trac. E.g. it would be nice to see what commits (to the central repo) where made on this ticket or what’s the last successful build for that ticket.
There are lots of fun, interesting and useful things to be done within git-buildbot-trac integrated system. Yet it requires some hands-on experience to check what’s the best corner to cut and the biggest pain to cure.
