On Sat, 1 Jan 2005 06:18:04 -0500, Ron Jeffries <[EMAIL PROTECTED]> wrote: > Running all the tests in one's sandbox before any kind of commit > seems to me to be basic, but perhaps it needs saying. > > I think we're talking about what happens after that: whether one > does as Beck and Jeffries et al. recommend, and builds on the build > machine, or whether one throws one's code at the asynch process > Jason describes.
OK. I think I understand where the disconnect was... What started this thread was the idea of doing all of the "pre commit" testing in an asynch process. (I guess, establishing that doing a build and test before check-in is NOT basic to everyone...) You, Jason and I agree that this is a "not good' thing. The other fork was doing the integration build by hand and waiting for the results vs checking code in and having an automated integration build happen. I think that whether you wait for the results or move on is a matter of convention, and in many cases, the integration build and test may well happen before you have a chance to start something new. But what if you have a "complete" set of tests that takes, say, an hour.... would you want to wait for that to finish before moving on, or, having done some sanity checks before checking is, is it better to move on and then go back to fix things if the build happens to fail (which may not be likely)? > When you and I walk over to the build machine and build, we are > focused on that, and yet have an opportunity to decompress, to talk > over what has happened, and to look out the window if any. > > When you and I throw our software over the wall to the asynch build > and go on coding -- which is the avowed advantage of the idea as I > understood it -- then when the build barfs, we aren't "there". > > That's my concern. If a team wants to wind up there, I guess it's OK > with me. If they're large enough, it's more likely to be needed. I > just don't think it's the basic starting point: it might be a point > you'd be driven to, but after four years of manual sync on a 14 > person team, I'm not sure why. Maybe we were just dull. Three questions about your expeciences: - Can only one team integrate/build at a time? - How long does the Integration Build take? - How often does the integration build fail when people check in changes only after a successful Private System Build/Test in their workspace? (Happy New Year ;) ) Steve -- Steve Berczuk | [EMAIL PROTECTED] | http://www.berczuk.com SCM Patterns: Effective Teamwork, Practical Integration www.scmpatterns.com 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/
