[Building Sakai] Praise/blame mechanism for builds.sakaiproject.org:8080

Stephen Marquard stephen.marquard at uct.ac.za
Thu Apr 22 02:37:18 PDT 2010


As I think this will probably help reduce the time between trunk getting
broken and fixed again, I think it's a good idea. 

Cheers
Stephen

>>> "Berg, Alan" <A.M.Berg at uva.nl> 2010/04/22 10:29 AM >>>
Hi fellow hard workers,

Anthony Whyte and David Horwitz have incrementally added Sakai 2.x
related projects and branches to the Hudson server at
builds.sakaiproject.org:8080 After increasing the servers memory it
looks like we have a stable service.

I was wondering if we should turn on the praise/blame mechanism so that
developers get emails when they break the build for their indie project
or a branch and also project leads for the indie projects. There is even
a funky plugin to send to twitter ( nice suggestion David :) ).
 
I want to make one point clear; developers that have historically
broken trunk are in general those that do the most work. If you don’t
change code it is easy to avoid breaking the build.  The intention of
the praise mechanism is only to catch broken builds early.

What is your thinking?

If agreed on either David Horwitz or I can configure Hudson for opt in
project lead email addresses, so feel free to make contact. 


Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg 





 
______________________________________________________________________________________________


UNIVERSITY OF CAPE TOWN 

This e-mail is subject to the UCT ICT policies and e-mail disclaimer
published on our website at
http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
+27 21 650 4500. This e-mail is intended only for the person(s) to whom
it is addressed. If the e-mail has reached you in error, please notify
the author. If you are not the intended recipient of the e-mail you may
not use, disclose, copy, redirect or print the content. If this e-mail
is not related to the business of UCT it is sent by the sender in the
sender's individual capacity.

_____________________________________________________________________________________________________
 


More information about the sakai-dev mailing list