On 05/19/2011 08:44 PM, Christian Legnitto wrote:
> On May 18, 2011, at 6:07 PM, Justin Wood (Callek) wrote:
>> Last I heard that the hg.m.o based Pulse is currently a poller for hg from
>> the Pulse server and doesn't encompass all hg repos. Thus has a delay behind
>> it which can be multiple minutes.
>> There is/are plans to get an hg hook up and running for pulse notices from
>> hg.m.o directly, Which will allow by default to get all repos and be
> I talked to mrz yesterday and reopened https://bugzilla.mozilla.org/show_bug.cgi?id=603029. Everything is working / ready but got sidetracked with Aravind leaving and me getting busy with rapid release stuff.
>> I'd love for tooling to use pulse rather than needing to poll, but imo with
>> our requirements on timing for most things hg and the tooling we use, that
>> we are not at a point where Pulse is a useable solution. LegNeato can
>> certainly correct me if I am wrong on any of these points.
> Once bug 603029 is fixed it should be instant. As an added benefit you also see commit messages from mozilla github repos (I haven't instrumented them all yet though).
will that work with hg.m.o/services ? If so, do you have an example on
how to use it ?
>> ~Justin Wood (Callek)
>> On Wed, May 18, 2011 at 7:35 AM, Axel Hecht wrote:
>>> how far are we with pulse notifications on hg.m.o?
>>> Also, is anyone using pulse messages in general for production yet?
> Bob's team is using it in production for the war on orange. QA has a prototype that will hopefully go into production soon (still trying to track down some timeouts at about the week mark, may be an IT issue).
> tools-pulse mailing list
Tarek Ziade - Mozilla Services