More criteria needed for when to run recipies (such as check in user)

[matt.c.hughes@…]

We have a script which runs nightly to increment the version number of our software. That change is committed by a user which generally doesn't commit any other changes. It would be nice to be able to check who committed a change and run a build recipie only for that user. In this case, we'd like to run unittests which take a long time to run.

[matt.c.hughes@…]

The attached patch adds a username file to the buildconfig database. The queue checks this username, if it is not empty, against the changeset author and only allows the build if they matches.

This patch also adds an error if the user specifies a minimum revision number that is greater than the max revision number. The revision numbers are converted to ints in the database, so that it is possible to delete pending builds using SQL when the revision range changes.

Unittests are included.

[matt.hughes@…]

The above patch doesn't seem to work on windows; it throws an error while upgrading the database. I'm going to seperate the username and revision number stuff into seperate patches and add a field that allows one to exclude checkins by username.

The revision number part of the patch will be seperate and may address #104.

[matt.hughes@…]

Adds author criteria to build configurations