[Buildbot-devel] Buildbot, mercurial and incoming hook

[Dustin J. Mitchell]

On Wed, Jun 13, 2012 at 8:26 PM, Tom Prince <tom.prince at ualberta.net> wrote:
> Patrick Marty <marty.patrick at gmail.com> writes:
>
>> Is it possible to overcome this limitation ?
>
> I don't use mercurial, but I suspect that there is nothing fundamental
> about this limitiation, just that the hook is only designed to handle
> the one hook. Depending on the details of when/how the incomming hook is
> called, it might be partly due to the fact that buildbot has some
> dependency on the order in which changes are added to the database.

I, too, have weak hg-fu, but I think that this is the reasoning behind
the Mozilla hgpoller, which only generates a change for each push,
rather than each changeset.  The hgpoller is dependent on a
server-side "pushlog" extension which stores information on who pushed
what and when.  It turns out that this extension is a maintenance
nightmare :(

It's possible that the incoming hook wasn't available when all of this
was written.

Dustin