[Buildbot-devel] force requests under original buildset

[Dustin J. Mitchell]

On Mon, Oct 8, 2012 at 1:09 PM, Jorge Gonzalez <gjorge at google.com> wrote:
> did you mean read-only?

I meant write-once, actually, but close enough :)

> Indeed. In fact, after sending my email I kept on looking at my DB in more
> detail and realized that forced rebuilds actually create yet another
> sourcestamp with everything remaining equal to the original with exception
> of its ID. This fact is making me consider starting from the Changes, and
> work my way up to Builds...  pretty much navigating all the object
> hierarchy.

And even that is error-prone..

> I take you want this because you are not assuming that changes will
> necessarily be brought into buildbot in a chronological order that honors
> their topological order in their original trees?

Correct -- and because chronological is not topological, even for
sequential-revision VCS's like SVN -- if I have a commit to 'trunk',
followed by two commits to 'branches/devel' that both fail, followed
by another commit to 'trunk', buildbot's status-reporting stuff will
report the final commit as having "fixed" the problem
(failedToSuccess).

I have daydreams about automatically bisecting changes, too - when
running behind, Buildbot would build the most recent commit first,
then successively try to bisect its backlog as time permitted.

Dustin