--- In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
> Part of the integration practice (continuous
> integration) is to verify that all unit tests pass at
> 100% before finishing. That, in turn, requires that
> the product can be built with the code to be
> integrated.
>
> Put another way, if you follow the XP continuous
> integration practice as described, you won't have
> this problem. Period.
>
> Quite a few people use Cruise Control to do
> continuous integration, with some form of automatic
> indication if the build or tests fail. That can be
> e-mail notification, but it's frequently like an Orb
> or a lava lamp that turns different colors depending
> on the build condition.
>
> In counterpoint, both Kent Beck and Ron Jeffries
> are on record as saying they prefer manual integration,
> and cite a number of reasons having to do with workflow
> and team dynamics for that preference.
>
> On another point: if a project has a continuously
> broken build over any substantial length of time,
> or they have broken builds frequently, I'd question
> whether they're "really doing XP". There's a fairly
> big grey area between "XP" and "not XP", but that
> is a characteristic that's on the wrong side of the
> line, IMO.
>
> HTH
>
> John Roth
Thanx John for you clear explanation.
Indeed, I confirm that the "breaking build projects" are on the
darkest grey area.
Actually the projects I am thinking of involve more than 100
developpers, which make them out of scope as only one XP project.
If I follow you advice, the solution should be to break them down on
smaller projects, each with their own "almost manual" continuous
integration.
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
