[Buildbot-devel] Making BuildRequests merging configurable, rfc

Axel Hecht l10n.moz at googlemail.com
Thu Jan 22 18:17:28 UTC 2009


Hi,

I'd like to get some comments on http://buildbot.net/trac/ticket/415 and
http://github.com/Pike/buildbot/tree/bug415.

Basically, I'm adding options to master.cfg on when to merge build requests,
plus the ability to give a completely independent implementation. From the
html-ified docs...

4.6 Merging BuildRequests

By default, buildbot merges BuildRequests that have the compatible
SourceStamps. Starting with 0.7.10, this behaviour can be customized to, for
example, only merge when the reasons match as well, or if the build
properties don't differ.

    Note: This feature is experimental, please provide feedback in the
mailing list on this. Future versions of buildbot might change the way this
functionality is exposed, too.

The default behaviour to merge BuildRequests with matching SourceStamps can
be overwritten by setting

     c['mergeMatchingRequests'] = False

Be cautious when doing that, as most VC steps will exhibit unexpected
behaviour when given Changes with mismatching branches.

To customize the behaviour such that only BuildRequests with the same reason
get merged, set

     c['mergeMatchingReasons'] = True

Another criteria on which merging can be controlled are build properties, to
switch those on set

     c['mergeMatchingProperties'] = True

These settings can be combined to only merge BuildRequests with matching
SourceStamps and matching build properties. All settings are taking effect
on all builders. If you need a higher level of customization, you can
specify your own class instance,

     c['loadMaster'] = MyLoadMaster()

....

I'd welcome feedback on design, configuration, and docs here or in the
ticket.

Thanks

Axel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090122/b698d56b/attachment.html>


More information about the devel mailing list