One build per Subversion commit

Given Subversion commits are atomic, it would be great if there was one Bamboo build run per commit.

At the moment, the project is put in the queue when a trigger is received, and when the build starts, it runs 'svn update', getting all changes up to HEAD. On a busy server, where a build might take half an hour to progress through the queue, this can mean three or four commits are bundled together in the same build.

The benefits of having a single build per commit is that it is easier to see exactly which commit broke the build.

In terms of implementation, Bamboo needs to record the revision number which triggered the build in its queue item. When that queue item is to be executed, Bamboo needs to update to that revision number, and run the build. If subsequent triggers come from the Subversion system while the first one is still queued, they must be put in the queue separately with their associated revision number.

Note: this is the opposite of BAM-926. I'm not sure exactly why those guys want Bamboo to collapse multiple atomic commits into one build. That seems illogical to me.