[Buildbot-devel] how can a slave build each revision separately, or do "background work"

[Charles Lepple]

On Dec 22, 2009, at 5:02 PM, Steven Knight wrote:

> I'm looking for some advice on how best to accomplish the following:
>
> 1)  Have a slave build+test each revision separately, even if  
> multiple revisions have been checked in while the previous run was  
> in progress.  (Yes, in theory this could cause the slave to never  
> catch up.  In practice, the rate of change is low enough that this  
> should never happen, and we'd deal with it manually in the unlikely  
> event it did.)  Barring an oversight on my part, I'm trying to  
> thread my way through the life of a BuildRequest to learn which  
> classes need to be affected to implement this.

As long as your change source sends every change (I'm not sure if all  
of the polling scripts do this), you should be able to use a  
mergeRequests function that always returns 'False':

http://djmitche.github.com/buildbot/docs/0.7.11/#Merging-BuildRequests

(Not sure about the answer to the second question.)