I address this with two features:
1. I parameterize my scripts. 2. I also extract all the data related to a
particular build (eg. a web site on a particular IP) to Xml. My build command
includes a parameter identifying the web site to be built. The script reads
the Xml and extracts all of the data, including source control information (eg.
trunk, branch, tag, version, etc), set properties, and executes the build. If
the build requires different processing dependent on source control or test
properties, they can be handled dynamically.
All of the information to initiate the build is in the command line, so running
the build manually or through CCNet is the same, ... just use the command.
The Xml data on a particular build also contains additional data defining IIS
configuration, web.config configuration, connection string configuration, CCNet
configuration, and description information used in a custom web site that
displays all of the managed web sites.
HTH
Curt
----- Original Message ----
From: Bob Archer <[EMAIL PROTECTED]>
To: nant-users@lists.sourceforge.net
Sent: Monday, February 19, 2007 2:18:00 PM
Subject: [NAnt-users] Brancing
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{
font-family:Arial;
color:windowtext;}
_filtered {
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{}
-->
I wonder if any one has set up a build that supports
building from different branches. For example, lets say you branch your
source to build a hot fix for a previous release? If so, how are you handling
this?
Do you create a new build script for the branch? Or, do you
have a property in your scripts that allows for a version tag or other
branching label in source control? What about sending publishing the builds?
How do you keep the branch build separate from the truck builds? Do you set up
separate
QA/Test virtual directories to test different branches?
How do you automate the branch build? Do you create another
project in CCNet for the branch?
Id love to hear how you guys handle some of these
issues.
BOb
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
