[TIP] RPC URLs in config for CI system

Robert Collins robertc at robertcollins.net
Sun Oct 4 03:29:14 PDT 2009

On Mon, 2009-09-14 at 09:48 -0500, Olemis Lang wrote:
> Hello guys!
> Imagine a world where a CI client (slave) reports build results to a
> CI server (master) via RPC . Under such circumstances, what would be
> the (right | best | std | ...) way to configure the URLs in the client
> so that it be able to connect to the server. Is there a way (URL
> schema or something ;o) to specify this ?
> Features that should be considered :
> 1 - RPC Transport (e.g. http, smtp, xmpp, ...)
> 2 - RPC flavour (e.g. JSON, XML, AMF ...)
> 3 - Server, port, path, ...
> 4 - RPC namespace
> My idea so far is to use a regular HTTP(s) URL and include the RPC
> namespace in fragments,
> i.e. something like `http://myserver.com/path/to/xmlrpc#ci.server.xxx`
> . In this case `ci.server.xxx` would be the RPC namespace .
> It should solve 3 and 4, probably 1, but definitely not 2

 #... is client side interpreted. So put your client specific stuff
there. I think that would work tolerably.

What do you mean 'RPC namespace'?
You could consider directory parameters to pass info across, but
strictly speaking they should be interpreted by the server not the
client, so it would be a little icky.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20091004/27912156/attachment-0001.pgp>

More information about the testing-in-python mailing list