92 lines
5.5 KiB
HTML
Executable File
92 lines
5.5 KiB
HTML
Executable File
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
<html>
|
|
<head>
|
|
<title>CruiseControl.NET : CruiseControl.NET Integration Process</title>
|
|
<link rel="stylesheet" href="styles/site.css" type="text/css" />
|
|
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
</head>
|
|
|
|
<body>
|
|
<table class="pagecontent" border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#ffffff">
|
|
<tr>
|
|
<td valign="top" class="pagebody">
|
|
<div class="pageheader">
|
|
<span class="pagetitle">
|
|
CruiseControl.NET : CruiseControl.NET Integration Process
|
|
</span>
|
|
</div>
|
|
<div class="pagesubheading">
|
|
This page last changed on May 19, 2005 by <font color="#0050B2">orogers</font>.
|
|
</div>
|
|
|
|
<p>The following is an example of what steps the CruiseControl.NET server goes through when running an integration on a project built using NAnt and checked into a Visual Source Safe (VSS) Source Control Server.</p>
|
|
|
|
<p>This process is basically the same for all other build tools and source control systems.</p>
|
|
|
|
<p><div align="center"><img src="download/attachments/701/image002.gif" border="0"/></div></p>
|
|
|
|
<p><img class="emoticon" src="images/icons/emoticons/warning.gif" height="16" width="16" align="absmiddle" alt="" border="0"/> This guide is only meant as an example. For exact configuration details, please refer to the documentation for the <a href="CruiseControl.NET Server.html" title="CruiseControl.NET Server">CruiseControl.NET Server</a> or <a href="Web Dashboard.html" title="Web Dashboard">Web Dashboard</a>.</p>
|
|
|
|
<ol>
|
|
<li>The <a href="CruiseControl.NET Server.html" title="CruiseControl.NET Server">CruiseControl.NET Server</a> is started, and a project is started according to a <a href="Project Configuration Block.html" title="Project Configuration Block">Project Configuration Block</a> in the <a href="Configuring the Server.html" title="Configuring the Server">Server's Configuration</a></li>
|
|
<li>CCNet checks the source code repository for modifications that have occurred since the last build attempt.
|
|
<ol>
|
|
<li>When modifications are detected
|
|
<ol>
|
|
<li>CCNet labels the project with CCNETUNVERIFIEDxxx (xxx = date/time) (Visual Source Safe only, optionally)</li>
|
|
<li>CCNet gets the latest version of the source from the source control repository</li>
|
|
<li>CCNet starts the build by executing the tasks in the <b><tasks></b> section of the <b>ccnet.config</b> file. In this example, the build will execute the <b><nant></b> task to run the NAnt build file.</li>
|
|
</ol>
|
|
</li>
|
|
</ol>
|
|
</li>
|
|
<li>NAnt processes the build script specified by the <b><nant></b> element . The following steps make up one possible scenario.
|
|
<ol>
|
|
<li>NAnt runs VS.NET using either the <b><exec></b> task or the <b><solution></b> task. The <b><solution></b> task provides better reporting capability for later steps.</li>
|
|
<li>NAnt runs NUnit using the <b><nunit2></b> task or the <b><exec></b> task</li>
|
|
<li>NAnt runs FxCop using the <b><exec></b> task</li>
|
|
</ol>
|
|
</li>
|
|
<li>CCNet receives the outcome of the NAnt execution (Success/Failed)
|
|
<ol>
|
|
<li>If the build was successful, CCNet replaces the CCNETUNVERIFIEDxxx label with the next sequential build number. (VSS only)</li>
|
|
<li>The XML output files are gathered from each step using the <a href="File Merge Task.html" title="File Merge Task">File Merge Task</a> and output as an xml file in the log directory specified in the <b><logDir></b> element.</li>
|
|
</ol>
|
|
</li>
|
|
<li>CCNet sends out email based on the <b><publishers><email></b> elements in <b>ccnet.config</b> (Optional).
|
|
<ol>
|
|
<li>If <b><group notification="change"></b> is set, then the individuals will only receive email if the status of the build changes (Success -> Fail, or Fail -> Success)</li>
|
|
<li>If <b><group notification="always"></b> is set, then the individuals will receive email for every build.</li>
|
|
</ol>
|
|
</li>
|
|
<li>CCTray displays current status of the build in the client system tray. The user can use the "Launch web page" menu item to browse to the build status website.</li>
|
|
<li>Project Dashboard enables multiple continuous integration projects to be viewed.</li>
|
|
</ol>
|
|
|
|
|
|
<p>Content supplied by Noel Gifford.</p>
|
|
|
|
<br/>
|
|
<div class="tabletitle">
|
|
<a name="attachments">Attachments:</a>
|
|
</div>
|
|
|
|
<div class="greybox" align="left">
|
|
<img src="images/icons/bullet_blue.gif" height="8" width="8" alt=""/>
|
|
<a href="download/attachments/701/image002.gif">image002.gif</a> (image/gif)
|
|
<br/>
|
|
</div>
|
|
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
<table border="0" cellpadding="0" cellspacing="0" width="100%">
|
|
<tr>
|
|
<td height="12" background="http://confluence.public.thoughtworks.org//images/border/border_bottom.gif"><img src="images/border/spacer.gif" width="1" height="1" border="0"/></td>
|
|
</tr>
|
|
<tr>
|
|
<td align="center"><font color="grey">Document generated by Confluence on Mar 14, 2009 02:55</font></td>
|
|
</tr>
|
|
</table>
|
|
</body>
|
|
</html> |