I think Troy has summed things up nicely. A small point to add to this discussion that I think is being implied by a number of posts: the build comes in a number of flavours. There's a Private build an Integration build and a Release build (and possibly other variants). Each build is a superset of the previous. For example, the Private build contains the core set of tasks such as Compile (optionally Clean), UnitTest, CreateDistribution (possibly). The Integration build adds to the tasks that the Private build performs eg Analyse, Document (possibly), and so on and so forth.
I think its good practice to try and separate out each task into a distinct target and then have higher level targets that pull together these individual targets that correspond to a Private build, Integration build and Release build. A developer can then execute the PrivateBuild target before check-in to increase the quality of the active codeline (aka trunk) without burning time waiting on a whole set of other tasks that are only really relevant for other build types. Christian 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 [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
