[TIP] RPC URLs in config for CI system
Olemis Lang
olemis at gmail.com
Mon Sep 14 07:48:30 PDT 2009
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
Thnx in advance !
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Introducción a la API de Google Analytics -
http://feedproxy.google.com/~r/simelo-es/~3/iRzT5_lZg4c/introduccion-la-api-de-google-analytics.html
More information about the testing-in-python
mailing list