clean up and add small functionality to a python file

CLOSED
Bids
2
Avg Bid (USD)
$180
Project Budget (USD)
$30 - $250

Project Description:
The buildbot master configuration file (master.cfg) is just a plain python file defining certain vectors; we have one for our buildmaster here that has grown considerably with time, with a lot of repeated stuff (see attachment).
We want to clean it up, drawing inspiration from the one for the webkit project:
http://svn.webkit.org/repository/webkit/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/master.cfg

But we do not want to objectify all (buildsteps, factories and builders), only the buildsteps; basically there would be buildsteps such as get_source_step(reponame), compile_step(workdir), extract_step(), qmake_step(project), make_step(project), test_step(cfg_file) that wrap all the platform-dependent stuff - pick up the platform from sys.platform (we have linux2, win32 and darwin).

The idea (for example for compile_step) is that instead of having separate linux_compile_steps, linuxclang_compile_steps, osx_compile_steps and windows_compile_steps vectors, at the end we want to enter just:

compile_steps = [ compile_step("src"), compile_step("dms"), compile_step("fc"), ... ]
flinux.addSteps(compile_steps)
flinuxclang.addSteps(compile_steps)
fosx.addSteps(compile_steps)
fwindows.addSteps(compile_steps)

And finally the small enhancement: add additional builbot steps information to waterfall for the test_step class, see:
http://buildbot.net/buildbot/docs/0.8.6/manual/customization.html#buildstep-urls
http://osdir.com/ml/python.buildbot.devel/2006-09/msg00025.html

The information we want to add is the number of tests failed (that you can retrieve from the return code of runner.py if positive and less than 128) and a link to the report in the form: /test_reports/buildslavehostname/summary.xml and a link to the logs in the form /test_logs/buildslavehostname/

Versions: the buildmaster runs on debian 7 (wheezy) so buildbot version is 0.8.6 and python version is 2.7.3.

Testing: what you can do is testing with "buildbot checkconfig .". You can not test RUNNING it ("buildbot start ."), unless you have a buildbot with the very same config as ours, therefore we will take care of that. You can optionally test running it with a simple buildbot setup (i.e. only on your development environment).

Skills required:
Python
Additional Files: stuff.zip
About the employer:
Verified
Public Clarification Board
Bids are hidden by the project creator. Log in as the employer to view bids or to bid on this project.
You will not be able to bid on this project if you are not qualified in one of the job categories. To see your qualifications click here.


$ 206
in 4 days
$ 154
in 3 days