buildbot, an automated build tool, development and release announcement list

Patrick Marty | 7 Jun 2012 15:49

Buildbot, mercurial and incoming hook

Hi everyone,

I am using buildbot with mercurial and I want to know why it is not
possible to use
the hgbuildbot hook with a 'incoming' hook, as explained here :

http://buildbot.net/buildbot/docs/current/manual/cfg-changesources.html#mercurial-hook

"The hgbuildbot.hook function will only work with the changegroup hook."

Is it possible to overcome this limitation ?
Is there a buildbot hook available for the 'incoming' hook type ?

Yours
Patrick

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Tom Prince | 14 Jun 2012 03:26

Re: Buildbot, mercurial and incoming hook

Patrick Marty <marty.patrick@...> 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.

  Tom

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Dustin J. Mitchell | 24 Jun 2012 16:59

Re: Buildbot, mercurial and incoming hook

On Wed, Jun 13, 2012 at 8:26 PM, Tom Prince <tom.prince@...> wrote:
> Patrick Marty <marty.patrick@...> 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

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

(Continue reading)