[Mailman-Developers] gsoc ci tool updates

varun sharma varunsharmalive at gmail.com
Wed Jul 9 12:25:01 CEST 2014


HI everyone,

I have been trying to implement the ci-tool a different way, instead of
changing the configuration in the source, i am now creating new
client/server files along with the new configuration. The main advantage is
that the source will remain untouched if someone just want to use the tool.
Also, in default config, i've added mailman, postorius, mailmanclient,
hyperkitty and kittystore. If someone wants to use it for different
projects, then he can simply change the config file of client and in that
case the tool will first look for those packages into the installed
packages and if it does not find them there, then it will look for absolute
path in config. Best possible case is when all the projects involved are
installed in virtualenv using 'pip install -e package'.

You can try it out by branching the repo

bzr branch lp:~varun/mailman/mmci
pip install -e mmci

For client:
mmciclient --create client_name
mmciclient --pull client_name
mmciclient --test client_name
mmciclient --try_ client_name

--create command will create a dirctory with client_name and further
subdirectories (config,logs,patches)

For server:
mmciserver --create server_name
mmciserver --start server_name


In the previous implementation, i was using project names instead of
client/server configuraion like:
ci-tool --pull postorius
ci-tool --test postorius

I think the former implementation is better as it can save multiple user
defined configurations for client and servers and it is bit more user
friendly. Suggestions on this implementation or how can i improve it
further are welcomed.


Thanks
Varun


More information about the Mailman-Developers mailing list