I think it may come as a surprise how many occasions you might make use of a separate script that setup the build environment:
- re-creating an old build - setting up a new machine - disaster recovery tests and (heaven forbid) the real deal - an actual disaster - the next team in the organisation to adopt the build / agile process - your next company - other users new to the community Also a related issue is what tools do you add to your version / source control repository. The benefit of having everything / significant proportion of the tools in repository is that you can label the version of the tools that was used to build your solution. Those tools that offer XCopy deployment really have the advantage here as you can include the tools under the directory for your solution and have a build management tool (eg CCNet) check-out *changes* to the tool in addition to retrieving the source files for your solution. Christian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anderson, Kelly Sent: 18 October 2005 04:08 To: nant-users@lists.sourceforge.net Subject: [Nant-users] Install Tools There is not really a right or wrong answer to this, but I am curious as to whether there is any point to installing tools as part of a build process. For example, one could go to the length of installing the compiler, code generators, revision control system, cruise control and basically everything except maybe NAnt from your build script. It would have the advantage of setting up the whole environment, and being able to have the environment be setup correctly from any machine that runs the script. This would be helpful if you had to recreate an old environment. It would obviously have the disadvantage of running much more slowly. I suppose a middle ground would be to have a separate NAnt script/target that did these sorts of installs, and you only run it when you are on a new machine, or something has changed... If you just expect the tools to be installed, then you have a job setting up a new machine, virtual machine or whatever. If you do this often, it might be worth automating, and it might be as easy to write a NAnt script to do this as to document the process. Any thoughts? What do you do to manage your tool sets? A similar question comes up as to whether to do a clean before a build every time, or just some of the time (say the nightly build) or just when manually requested. These clean builds are useful from time to time especially if files have been deleted from revision control, and you want to make sure everything still works, but they can also be very slow for a Continuous Integration environment. -Kelly E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users Click https://www.mailcontrol.com/sr/RFmF8TNGtc+wwfYi9yV+DZqdnghaIs5bXNWflshhmlT3PGmgKnBNHPg9S2L9kyLYXl+Qbf!g8YSjCDGYl4BhzN0xmMYkZ15SAX1wHMVcENsND2BkyqCMcYfGL1wjg7As4UMSV6ABxPpqYRvjeUWmlVXDNR7ViAKXPgREuITD7o5gVxydMwfm+DtrJfE1IKy4HUlld04P2RwTaHMufpFg!lw1kG9AUq7M to report this email as spam. This e-mail, and any attachment, is confidential and is intended only for the use of the individual to which it is addressed. If you have received it in error, please delete it from your system, do not use or disclose the information in any way. The contents of this message may contain personal views which are not the views of the ECA Group, unless specifically stated. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
