[Buildbot-devel] Status of hg polling

Georges Racinet gracinet at anybox.fr
Sat Jun 2 19:09:47 UTC 2012


On May 29, 2012, at 8:07 PM, Moore, Mathew L wrote:
>> 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.
>>
> <snip>
>>
>> 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.
>>
>
>
> Interestingly, I just today signed up for the mailing list to also  
> ask about the status of Mercurial polling.  Searches online only  
> pulled up links like the pushlog ones mentioned.

That is a funny coincidence, indeed :-)

>
> I take it from the discussion that there is no direct solution  
> available, but is there a "best practice" or suggestion for handling  
> the case where one does not have access to the Mercurial  
> installation where the repo is hosted (i.e., no hgbuildbot.hook)?

What I've been doing so far is setiing the hook in a local clone and  
perform pulls in a cron job. Indeed, these hooks react in the same way  
if new changesets are added by a pull command. Since I've been doing  
that for big collections of repositories, I call that "mirroring".

I had to do that even for software I actually maintain, just because I  
wanted to setup private buildbots for several customer projects that  
depend on that software and I felt that adding hooks for all of them  
in the public reference repos was wrong (did not think at that time  
that the hooks can't push changes to several buildmasters anyway).

Since I'm also a recent user, I can't say if that's considered  
standard or best practive, but I'm a bit tired of it. In particular,  
it makes experimental setups long to create.

Anyway, there's some progress, see http://trac.buildbot.net/ticket/ 
2307. If you want to give it a try, feedback would be really useful,  
but it's definitely not ready for production.

Cheers,

>
> I'm a beginner user of Buildbot, but love it so far.  Thanks for all  
> of your efforts toward its development.
>
> --Matt





More information about the devel mailing list