[Buildbot-devel] force requests under original buildset

[Jorge Gonzalez]

This is a conceptual question on Buildbot's buildsets, buildrequests and
sourcestamps. I'm on 0.8.6

The internal concept of buildset within buildbot seems to serve (at least)
the purpose of grouping together a set of build requests on different
builders for a given sourcestamp. This is useful since one can then define
whether a certain change (its sourcestamp, really) broke "anything" by
looking at the results of all build requests that stemmed from it when it
was scheduled. This, in essence, is equivalent to saying the
"health" of buildset is defined by the health of all its "constituent"
build requests.

Under this light, would it make sense to have a  way to force *re-*builds
that doesn't create a completely new buildset to contain the new request?
Right now it seems that when a build is resubmitted from the
builder/<nr>/builds/ view, a new buildset & build request pair is created
for it.

In case it matters, the motivation behind this is that I am actually using
the internal buildset ID as a canonical number for my team and using to
display the overall effect of a change in a custom version of the tgrid
GUI. Builders' build numbers are not enough since we want to be able to say
/ display whether a certain change broke any of the targets it affects. I
know the console view is meant to provide something along these lines, but
it frankly never worked correctly for me.

Jorge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20121004/8cce4dc3/attachment.html>