Steve Berczuk writes: > This is basically the idea behind the dependency structure in > the SCM pattern language between Private System Builds, > Integration Builds, and the various kinds of tests. > > http://www.scmpatterns.com/book/pattern-summary.html > or > http://www.scmpatterns.com/book/refcard.html > with the emphasis on more frequent integration, perhaps at > the expense of "better" yet longer running tests.... (Note, > that I probably need to better define the distinction between > smoke, unit, and regression tests)
What he just said! > > The smaller the time-frame between commits, the more I'd > like to have > > an automated setup. //But I want one that pushes code to > all the other > > developers, keeping the sandboxes synchronized.// Clearcase can do this, by virtue of its virtual filesystem. I cant recall coming across a developer that ever preferred it to happen this way rather than having control over when their own sandbox (workspace) gets updated. Usually they just want notification to alert them when it happens. Most extreme case is they want some kind of dialog/alert to pop-up to say "Joe has commited his change "foobar" to the codeline - would you like to automatically update your sandbox to the latest state of the codeline?" with options like yes, no, and "more info" where I can look at a summary of joe's changes, and "drill-down" to view a diff-package if desired. > We've had this discussion before. The trick is to not be > disruptive. I suspect ALERTING someone that there was a > change should be good enough (and we all update from the > repository every few minutes when we're not actively coding > anyway, right ? ;) ) We have an article on this as well, regarding "Codeline Merging & Locking: Continuous Updates and Two-Phased Commits" (See <http://www.cmcrossroads.com/articles/agilenov03.pdf>) it talks about a post-commit notification to implement such alerting so others can do "Continuous Workspace Update", as well as several different flavors and levels of synchrony/asynchrony to ensure proper-commit protocol and codeline consistency/integrity for a two-phased codeline commit. -- Brad Appleton <[EMAIL PROTECTED]> www.bradapp.net Software CM Patterns (www.scmpatterns.com) Effective Teamwork, Practical Integration "And miles to go before I sleep" --Robert Frost 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/
