On Fri, 7 Feb 2003, Peter S. Hamlen wrote:
> Date: 07 Feb 2003 11:53:03 -0500 > From: Peter S. Hamlen <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: RE: [OT] how do people work in project with one CVS server > > Just to add two more recommendations to Craig's list: > > * Have an automated build process that builds from scratch and > runs your tests. Run this process at least once a day (cf. the > nightly build process for Struts and other Jakarta projects.) > This ensures that if someone does "break the build", it gets > detected quickly. We run builds hourly. > Some large scale projects, especially those that need to run on multiple architectures, often have build processes that run continuously on different types of machines -- Mozilla uses their TinderBox for that, for example. IIRC, SourceForge offers a compile farm for things like this as well. > * In our case, we also have a developer "build" account which developers > can log into and kick off a build. Most of us get in the habit > of running a build from this account just after we check in. It > catches all those annoying "oh, forgot to check in a file" and > other issues that arise because your development machine is > slightly different than the standard (and then you scramble > to fix the build before anyone notices and you have to > buy the beer!) > I do something similar to this to create the nightly builds for Struts and a bunch of the commons packages -- a cron job that checks out the sources separately from my development directory, and runs the complete build. I've only had to buy myself a beer once :-). > -Peter Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
