On Thu, 30 Dec 2004 13:35:10 -0000, bernard_notarianni <[EMAIL PROTECTED]> 
wrote:
> 
> 
> --- In [EMAIL PROTECTED], Ron Jeffries
> <[EMAIL PROTECTED]> wrote:
> > How will this program solve the problem of people not caring about
> > the build being broken?
> 
> Because they cannot commit their work is the source repository until
> the build work (and potentially the unit test as well)
> 
> Of course, this does not solve problem of people not caring about
> commiting their work in the source repository... but as this level,
> should we still care about them? :-)

A few  thoughts:
 1. If people don't care, automation is, a best, a band-aid solution.

 2. The automated mechanisms that the BLOG describes have been around
for a while.

 3. Good practice is for a developer to do a Private System Build and
some sort of Smoke Test before checkin anyway... If developers don't
care enough to do this, then automating this through the SCM system
won't solve the underlying problem (Lack of care for quality)

 4. if (3) is true, you could get the same result with an ant target
that updates, builds, tests, and checks in code only if the other
steps work. This DOES require the developer to take action, but so
does executing a "check-in" And this solution would be simpler.

 5. In my experience, you may still have conflicts after doing this
sort of test if you don't serialize checkins, and in a large team,
integration token approaches can slow things down A LOT. On the other
hand, as long as you have a way of testing the build after each
checkin, you can generally catch the problem soon enough to fix it.

So, I'm kind of with Ron on this: This is a very heavy weight solution
to a problem that can be addressed in a much simpler way.

-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/
 



Reply via email to