Date: Wed, 23 Nov 2011 08:09:24 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Jesse Young <jlyo@jlyo.org>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] build server messaging
Message-ID: <20111123080924.11e3e72b@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <20111122191018.2df62a73@telperion.jlyo.org>
References: <20111122165940.6c0e0371@ncopa-desktop.nor.wtbts.net>
	<20111122191018.2df62a73@telperion.jlyo.org>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 22 Nov 2011 19:10:18 -0600
Jesse Young <jlyo@jlyo.org> wrote:

> On Tue, 22 Nov 2011 16:59:40 +0100
> Natanael Copa <ncopa@alpinelinux.org> wrote:
> 
> > Hi,
> >
> > Our current messaging between git server and buildservers goes via
> > public IRC and has not been 100% reliable.
> >
> > So I have been looking at replacing it with a zeromq[1] based infra.
> >
> > The idea is that we have a buildmsg-server that listens on 2 ports,
> > one for subscribers and one for git push notifications.
> 
> I'm not familiar with the build system, and only minimally familiar
> with zmq, so ignore me if I'm totally off base.
> 
> The way I understand how zmq subscription sockets work is that
> clients will miss notifications if they get disconnected for whatever
> reason. So a mechanisim should be in place to replay notifications
> that the client may have missed.

It is not really a big problem since what the build server does
when it gets it notification is pull from git and build all that has
been changed (or more precise, build everything that is missing). In
other words it will pick up everything it has missed while it was
offline.

zeromq is pretty nice in that way, that if the subscriber start up
before the publisher, it will auto connect whenever the publishing
server (buildmsg-server) server comes up.

If the buildmsg-server goes down people who does a git push will notice
it since the git notification will block til server comes back up again.

> Maybe this is the non-reliability
> you're experiencing with IRC as well?

Not really. I think the build bot does not handle all kinds of stuff
that might happen with a public IRC server. (irc server goes offline,
comes back, you get kicked from the channel etc etc).

The problem is that we don't have control over the messaging server
which currently is Freenode.

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---