ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: Looking for a Build Philosophy
Date Thu, 17 Oct 2002 19:30:19 GMT
Sadly, I'd have to concur with Scott. Treats are not enough, especially in a
distributed environment where people are in at least 3 cities, if not
working from home. We have all the right intention/process in place,
published, etc... and still people don't write test, and half the time write
so-so code. Thankfully we have nightly builds and CruiseControl running, and
things have settled down a bit, but the carrot is not enough in my mind, and
the stick should have been handled more often than not. I'm afraid nothing
will ever replace good personal code hygiene, except perhaps true XP with
pair programming to learn from your peers, and have them look over your
shoulder half the time.

PS: I used Continuus CM (old name for CM Synergy) in another lifetime, and I
loved it. It's too process-heavy as they say here...

-----Original Message-----
From: Chappell, Simon P [] 
Sent: Thursday, October 17, 2002 2:09 PM
To: Ant Users List
Subject: RE: Looking for a Build Philosophy

>developers who are used to doing things a certain way (being 
>however they feel like doing it that day), you are going to be 
>very hard pressed to get them to change.  That being said, if 
>you can get a change in place you must also have a system in 
>which to enforce and in some cases punish those that are 
>violating the structure.  Without that good luck.  Have 
>developer performance reviews be negatively affected by 
>habitual build breakers.

Ouch! I know that we had to bring in treats if we broke the build, but that
was in fun. Your suggestion doesn't sound like fun to me.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message