We could and can build everything from the repository since we tag everything for each build. However disk space is cheap, so we keep the built version around.
Also, we have several internal framework projects, libraries etc that other projects depend on, but those projects use different versions. Each project then copies the dlls (does not build then)from the appropriate folder on the build server to get the right framework dll. After we do a release to production, we clean up the build server to only keep the version that was actually deployed. During an iteration, we could build our app 50 times, but build 50 is the only we keep after production release. Jason > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Landes Eric (RBNA/CIT4.2) > Sent: Thursday, January 08, 2004 11:53 AM > To: [EMAIL PROTECTED] > Subject: RE: [Nant-users] Newbie question on using nant to > push to production > > Jason, > I assumed that you copied your bits from dev on up. That's > the way we would do it as well. > > I see you say that you have builds archived as well. Do you > do this in addition to your source control repository? It > seems that I could rebuild based on a label in my source in > case something came up as well. > > Eric [snip] ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
