Ron Jeffries wrote:
> On Saturday, January 1, 2005, at 10:50:09 AM, Steve Berczuk wrote:
>> - How often does the integration build fail when people check in
>>changes only after a successful Private System Build/Test in their
>>workspace?
>
> Occasionally. Each time is an "occasion" to reduce the chance of it
> happening again. Common causes that I recall are:
>
> - someone integrated improperly before, left the system in an
> unknown broken state. (yes, I know that Jason's approach, or
> Cruise Control "fixes" this.)
What CruiseControl "fixes" is leaving the system in an unknown state,
either good or bad. It's an information source, which is good. It's also a
safety net, which is good. Finally, it's a source of historical
information: how often does the team integrate, and how often does it
succeed. That's good too.
Furthermore, there is nothing in CruiseControl which prohibits manual
builds. In fact, you can even set up CruiseControl so that it only really
does builds when prompted through the admin interface; on my current
project, we have it set up exactly like that. Developers trigger builds on
demand.
Is it needed? No, of course not. Does it help? Well, it can. It's also a
good way to step towards a continuous integration practice; by having an
information radiator on how often the build gets broken, you can raise
awareness within the team of how their "sloppy" practices impact others.
Finally, in some teams, a dedicated build machine may not be possible to
obtain because the management lives on a shoestring budget. A build server
can be shared.
--
"Software is too expensive to build cheaply"
Robert Watkins http://twasink.net/ [EMAIL PROTECTED]
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/
