[Buildbot-devel] How does build request merging work?

[David Coppit]

On Mon, Mar 21, 2011 at 11:47 AM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:

> On Mon, Mar 21, 2011 at 10:40 AM, David Coppit <david at coppit.org> wrote:
> > To confirm my understanding, this query:
>
[snip]

> > Would show how a single buildername+build number pair would map to
> multiple
> > build numbers, build requests, sourcestamps, and ultimately changes.
>
> Not at all - in fact, I'm having a hard time figuring out what you
> meant to do.  First, in the URL, you're putting 'number', which is
> 'changes.number', after the '/builds/' component - that should be a
> build number instead.


Doh. This must be one of the changes that the team made before we inherited
the codebase. (I always worry about this scenario when emailing the list.)
We have a builds table with a build ID, build number, build request ID,
start time, and finish time.


>  Second, you're asking how a single
> buildername+build number can map to multiple build numbers, which
> doesn't really make sense.


I misspoke. I meant a single build number mapping to multiple build IDs.
That appears to be the case in our DB.


> The merge process begins by finding the best build request to start
> with (using nextBuild).  It then tries to merge that request with
> *all* other requests (using mergeRequests).
>

Thanks for the clarifications. We may have borked the merging, or I might be
looking at the data incorrectly, measuring backlogs of buildrequests that
are not actually indicative of system performance. I'll go off and dig some
more.

Thanks again,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110321/5d6252fb/attachment.html>