On Tuesday, February 26, 2002, at 01:02 PM, Paul Franz wrote:
> I assume that "Every time someone checks in new code, fire off a build" > has a set minimum time. Up to the user. CC has a minimum wait between cvs mods, so that people have some amount of time to finish a checkin, and a minimum check wait time, so that you are not hitting the repository constantly. The default is a five minute wait since the last modification, and an attempt every 30 sec. > This assumes also that whenever a person checks in code that it > compiles. Yep. If you check in broken code, you get a snidemail telling you where the errors are. To me, this is simple courtesy in a build system that has many users and contributors. > lso, do the constant builds produce the artifacts of the build (output > a jar ,ear files, etc. each time)? Up to you. You tell it what target to execute, and that target is expected to do whatever it is that you want done every checkin. In our case, it is a full build with a clean step and production of jar files. This takes about 7 minutes with our current code. Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
