On 9/18/06, Lakshman Srilakshmanan
<lakshman.srilakshmanan@tradingpost.com.au> wrote:
> Hi Peter,
>
> Not sure if running a build at pre-commit is a good idea.
[ snip ]
> Reason 3
> --------
> It could take day(s) to fix the problem in trunk. So during this period
> no one else can commit any work. I believe the risk of loosing source
> code from a developers machine is greater than a trunk that does not
> build.
>
>
>
> If your concern, is to ensure that code committed into trunk builds,
> then you should install a continuous integration build system like
> CruiseControl to be triggered post commit and inform the development
> team of failure immediately so that the error can be detected and
> corrective action taken. This could be a rollback of the change or get
> the developer to fix it.
This also allows the commits to be checked simultaneously on several
different configurations, so that you know your changes are valid on
all supported platforms (or the ones most easily broken? :-)
Subversion itself uses buildbot for the purpose (See http://mobsol.be/buildbot/)
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 18 10:47:48 2006