[Buildbot-devel] Status of hg polling

[Georges Racinet]

Le 27/05/2012 21:47, Georges Racinet a écrit :
> On May 27, 2012, at 8:52 PM, Dustin J. Mitchell wrote:
>> On Sun, May 27, 2012 at 12:22 PM, Georges Racinet 
>> <gracinet at anybox.fr> wrote:
>>> what's the current status of Mercurial polling in Buildbot ? There 
>>> is no such thing mentionned in the documentation. I've seen this 
>>> stalled pull request, based on the pushlog extension : (...)
>>
>> The pushlog extension has caused a fair bit of pain for Mozilla, as it
>> tries to keep in sync with the mercurial repo, and sometimes fails.
>> So I'm not sure we should be recommending adding it.
>
> And it's not standard, which means that the admins of the reference 
> repos have had to install it.
> I'd prefer something more universal anyway. Is there something based 
> on hgwebdir RSS feed or even on the Mercurial protocol itself 
> (whatever the transport layer) ?
After a quick read of GitPoller and its tests, that doesn't seem very 
hard to adapt to Mercurial. What it relies on is fetching the changes by 
calling the git executable in a subprocess.

I don't know if importing mercurial from python could further allow to 
avoid actually transmitting the changesets, but that would be much 
harder to maintain anyway, as it's officially not stable (some 
experience with Mercurial internals, here)

A question though : I see that BzrPoller is in contrib while GitPoller 
is in the main package. What's the reason ? If I were to try and 
contribute some generic HgPoller (with tests), where should I put it, then ?

Buildbot is a great piece of software to me, so I'd be very glad to 
contribute back.
Conversely, a generic HgPoller would make my setups more standard. They 
are currently heavily based on custom mirroring to gain control of the 
hooks while letting the reference repositories untouched.