Listing 5.1 in C#.NET

Creator QR-Code in C#.NET Listing 5.1

< xml version="1.0" encoding="utf-8" > <dashboard> <remoteServices> <servers> <server name="local" url="tcp://localhost:21234/CruiseManager.rem" allowForceBuild="true" allowStartStopBuild="true" backwardsCompatible="false" /> <server name="dotnet3" url="tcp://dotnet3:21234/CruiseManager.rem" allowForceBuild="true" allowStartStopBuild="true" backwardsCompatible="true" /> </servers> </remoteServices> <plugins> <farmPlugins> <farmReportFarmPlugin /> <cctrayDownloadPlugin /> </farmPlugins> <serverPlugins> <serverReportServerPlugin /> <serverLogServerPlugin /> </serverPlugins> <projectPlugins> <projectReportProjectPlugin /> <viewProjectStatusPlugin /> <latestBuildReportProjectPlugin /> <viewAllBuildsProjectPlugin /> <viewConfigurationProjectPlugin> </viewConfigurationProjectPlugin> </projectPlugins> <buildPlugins> <buildReportBuildPlugin> <xslFileNames> <xslFile>xsl\header.xsl</xslFile> <xslFile>xsl\modifications.xsl</xslFile> </xslFileNames> </buildReportBuildPlugin> <buildLogBuildPlugin /> <xslReportBuildPlugin description="FxCop Report" actionName="FxCopBuildReport" xslFileName="xsl\FxCopReport.xsl" /> <xslReportBuildPlugin description="NUnit Details" actionName="NUnitDetailsBuildReport" xslFileName="xsl\tests.xsl" /> <xslReportBuildPlugin description="NUnit Timings" actionName="NUnitTimingsBuildReport" xslFileName="xsl\timing.xsl" /> <xslReportBuildPlugin description="FxCop Report"

actionName="FxCopBuildReport" xslFileName="xsl\FxCopReport.xsl" /> <xslReportBuildPlugin description="NCover Report" actionName="NCoverBuildReport" xslFileName="xsl\NCover.xsl" /> <xslReportBuildPlugin description="Fitnesse Report" actionName="FitnesseBuildReport" xslFileName="xsl\fitnesse.xsl"/> <xslReportBuildPlugin description="MSBuild Report" actionName="MSBuildBuildReport" xslFileName="xsl\msbuild.xsl"/> </buildPlugins> </plugins> </dashboard>

localhost and dotnet3. The Web Dash-

board communicates with them using a remoting endpoint. You can define as many servers as you like. You separately configure all the view levels for the server farm C, for the servers themselves D, for the projects E, and for the builds F. This example sets up several build reports to be included in the Web Dashboard feedback. If you look closely, you ll see several tools like NUnit, FitNesse, FxCop, and others that we haven t discussed yet. Don t worry about what these tools are and what they do; we ll discuss them in upcoming chapters. Figure 5.3 shows the build-level view at the CCNet Web Dashboard as configured from listing 5.1.

When you first install CCNet, none of the build reports from other applications are included. You need to activate them through the Administrator Dashboard. Before the first time you use the Web Dashboard, you have to edit the dashboard.config file (you ll find it in %ProgramFiles%\CruiseControl.NET\webdashboard) and change the initial password in the <administrationPlugin> tag. When you re finished, click the link in the Web Dashboard s main page, enter the Administrator password, and then enable the tool reports you want to include in the Web Dashboard report. As you can see, you can have full control over the CCNet Web Dashboard. You can write your own plug-ins or obtain plug-ins from the internet. But to have so much control, you have to pay a small administration cost. The Web Dashboard gives you detailed information, and you can use CCTray to get a quick snapshot of what s happening on your build server.

CCTray is an application that s installed on each developer s workstation. You can download it from the home page of your CCNet Web Dashboard or directly from the ThoughtWorks website at http://ccnet.thoughtworks.com/. It sits in the Windows Notification area, commonly called the Task Tray. It manifests itself with this icon: CC . To configure CCTray, open it (double-click the icon) and choose File > Settings (see figure 5.4). You need to configure the noise level here as well. You don t want to be interrupted by messages about projects in which you have no interest. Try to keep the noise level as small as possible. Allow only information that s necessary to help you react when the

code quality degrades. Choose only the projects you need to see (see figure 5.5). On a fresh installation, you need to add a new CCNet server. To do so, go to settings (File > Settings) and click the Build Projects tab. Click the Add button. In the Project window, click Add Server. The easiest way to connect the CCNet server is over a dashboard: type the CCNet dashboard URL in the window. Keep in mind that if you re connecting to the CCNet server from another machine, you must add a firewall exception (port 80 on a standard IIS installation). CCTray uses a red/green indicator, similar to what you find in unit test tools. A

CC green tray icon indicates that everything is running fine. A red CCTray icon means you have to act. First, you must know where the problem is. The best way to get this information is via Web Dashboard. You can reach the CCNet Web Dashboard directly from CCTray: right-click one of the configured projects, and choose Display Web Page, as shown in figure 5.6.

Figure 5.5 Configuring CCTray. One CCTray benefit is the ability to work with more than one CruiseControl.NET server.