Thanks for the info Jason, that makes sense. If you have the time to answer, I have another question related to this. Let's say I've gone to production with my build. It's created the db for me, populated the web app, etc. Now I've been doing some maintainence work, which includes some new stored procs, and i've had to alter a table or 2. I'm wondering how I have this structured in my project(s) so this happens in the automated build.
I'm imagining a scenario where the developer(s) have a web application, and a database project. The way we currently do things is to use a cmd file with OSQL commands that execute the create/modify sql scripts. We would also have our create, alter, etc. as sql scripts in a database project. I don't want the new build to rebuild the database, I just want it to run the change scripts. Are you doing it this way, or are you extracting the data from the database, rebuilding, then repopulating with the data? I'd rather do the update scripts, but I don't see how I can accomplish that without manually intervening in the build files. TIA Eric L. -----Original Message----- From: Morris, Jason [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 4:25 PM To: [EMAIL PROTECTED] Subject: RE: [Nant-users] Newbie question on using nant to push to production 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 ------------------------------------------------------- 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
