[Buildbot-devel] Buildbot supporting buildset with multiple repositories

[Dustin J. Mitchell]

On Mon, Nov 14, 2011 at 6:08 AM, Harry Borkhuis <borkhuis at aeteurope.nl> wrote:
> Is there any kind of thought about this problem within the Buildbot team how
> to handle this problem?. We can imagine that more Buildbot users have
> problems with this.

Indeed, this is a variant on a common theme.  Most often, users differ
on how they define "at the same time", or what revisions to use on
repositories that did not change.  It sounds like you've defined those
well for your case, but that is not necessarily the only way to do so.

> Our proposal is to group sourcestamps into a set of sourcestamps, where each
> sourcestamp has changes from its own repository
>
> A MultiRepositoryScheduler should be configured with a set of repositories
> and installs it’s own filter (or changes a passed filter accordingly).
>
> The MultiRepositoryScheduler should pass the following information to the
> Build:
>
> a set of SourceStamps that contains the revisions of the repositories

This is similar to a proposal that's been discussed on and off for a
while: aggregate sourcestamps, that represent sourcestamps from a
number of repositories.  Figuring out exactly how to implement this
has been tricky, though: how can we best represent such sourcestamps
in the database?  How should they be generated?  How should Source
steps interpret them?

> Are there more requirements that we have to take into account when making
> these additions to Buildbot.

As always, backward compatibility is the tricky point.

I'll be happy to discuss this further - I'd *love* to see something
like this upstreamed into Buildbot!

Dustin