[Buildbot-devel] how to link gerrit change to repo

[Dustin J. Mitchell]

Apologies for not replying to this earlier - I wanted to read up on
gerrit a bit first.

On Fri, Oct 8, 2010 at 3:18 PM, Pierre Tardy <tardyp at gmail.com> wrote:
> I'm looking on how to implement use cases 1 and 2 with the same
> mechanism. I have idea on how to hack 2 with repo source fetcher
> looking on specially crafted property, but I'm not very happy with it.
> It is possible to report the user the list of old changes and let him
> trigger a build by selecting several of them?

This is a case where other forms of "try" support would benefit, too.
It seems like these cases should follow the lines of Buildbot's "try"
support, rather than being represented as changes.

Could the poller "fold" the multiple patches into one patch, somehow?

> In the case of several change happening quickly (and low number of
> slaves), I've seen buildbot grouping changes in one build. This
> behaviour is what is needed for change-merged event types, but not
> with 'patchset-created' wich are more frequent and which really need
> one build per change.

I believe that try builds do not get merged, so you should be OK there.

Dustin