Which gets me asking, if not NAnt for deploying, then what? I'm in the same place as Payton in using NAnt for some deployment. The goal is to have the nightly build complete and install itself onto the web and app servers and then kick off the automated tests if the build was successful. Our application(s) aren't that complex so I think it's possible with NAnt.
Right now, I'm working on the first part of getting it to install and run nightly. Test automation, if it ever happens, comes next. MArk B. -----Original Message----- From: On Behalf Of Brad Wilson Sorry, but I disagree with general "transactionality". A build is not a deploy. If you choose to use NAnt for a deployment, then that's fine; you may want to approach some kind of transaction support for a deployment task that you might write for yourself. But for general build purposes, there's just not enough value in my experience. - Brad On Mon, 24 Jan 2005 14:53:38 -0600, Byrd, Payton <[EMAIL PROTECTED]> wrote: > I just finished reading the NAnt release schedule and noticed there are not > any documented plans for adding transactionality to NAnt. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
