Realizing Continuous Integration With Cruise Control.Net (CC.Net)

Realizing Continuous Integration with Cruise Control.Net (CC.Net)

Cruise Control

Cruise Control is a free and open source build scheduler implemented using the .Net Framework. It is composed of the following two components:

1. Build Loop: The build loop is designed to run as a background process, that periodically checks the defined repository for changes in the codebase, builds it and provides the status as the final output.
2. Reporting: Cruise Control provides a reporting application to browse the results of the builds and provides a dashboard for the visual representation of the status.

As mentioned in my last article Cruise Control works with many source control systems. (Some of the better known are TFS, SVN, and VSS and so on.) Input for the build process is any parseable format so it can be integrated with any build tool (MSBuild, Nant, Maven and so on) that produces a parseable format. In addition to that this is widely used because of its extensive documentation. It also provides the option of a Mailing list.

Process of Cruise Control

1. Developer Checks-in the code
2. Cruise Controls polls the Version control system (Repository) to see if there are any changes in the codebase
3. If the changes are there, then Cruise Control triggers the build using the defined build tool, captures the build data and produces the Build Status Report

CCTray

It is a standalone application that enables the developers or any other team member to check the status of the builds on their local machines that can access the CC.Net Server.

High Level Architecture of CC.Net



Setup Cruise Control.Net

First of all download CC.Net EXE (CruiseControl.NET-1.8.3.0-Setup.exe) from http://sourceforge.net/projects/ccnet/

Run that EXE as Administrator. When installing, select all three components.




 
After the installation is complete, you can now access the dashboard by typing in the following URL:

http://localhost:8080/

At the physical path of installation you will see that there are three folders that were created named:

1. webdashboard
2. Examples
3. server

In the "server" folder there is a file named "ccnet.config". Open this file to do the configuration for automated builds. We need to add four blocks named:

1. Project Configuration Block: Information about the project that needs to be built, there can be multiple projects present in this config
2. SourceControl block: From where the code needs to be checked out for the build
3. Tasks block: Steps/process of the build
4. Publishers block: Generate output and produce reports (if needed, dispatch emails also)

For adding these you can either refer to the links above or I am providing you with the sample config below:

<cruisecontrol xmlns:cb="urn:ccnet.config.builder">

    <!-- This is your CruiseControl.NET Server Configuration file. Add your projects below! -->

    <project name="Sample Application">

        <webURL>http://localhost:8080/ccnet/server/local/project/SampleApplication/ViewLatestBuildReport.aspx</webURL>

        <!--set the sourcecontrol type to subversion and point to the subversion exe-->

        <sourcecontrol type="svn">

            <executable>C:\Program Files\TortoiseSVN\bin\svn.exe</executable>

            <workingDirectory>

        <PATHOFYOURAPPLICATION>\SampleApplication

      </workingDirectory>

            <trunkUrl>

        <REPOSITORYPATH/URL>/SampleApplication

      </trunkUrl>

            <autoGetSource>true</autoGetSource>

            <username>XXXX</username>

            <password>XXXX</password>         

    </sourcecontrol>

        <triggers>

            <intervalTrigger name="Cruise Control Continuous Integration" seconds="60" buildCondition="IfModificationExists" initialSeconds="30" />         

    </triggers>

        <tasks>

            <!-- Configure MSBuild to compile the updated files -->c:\

            <msbuild>

                <executable>c:\windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe</executable>

                <workingDirectory>

          <PATHOFYOURAPPLICATION>\SampleApplication\

        </workingDirectory>

                <projectFile>SampleApplication.sln</projectFile>

                <buildArgs>/noconsolelogger /p:Configuration=Debug /nologo</buildArgs>

                <targets></targets>

                <timeout>60</timeout>

                <logger>C:\Program Files (x86)\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger>             

      </msbuild>

            <exec>

                <executable>del.bat</executable>

                <buildArgs></buildArgs>

                <buildTimeoutSeconds>30</buildTimeoutSeconds>             

      </exec>       

            <exec>

                <!--Call mstest to run the tests contained in the TestProject -->

                <executable>C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe</executable>

                <baseDirectory>

          <PATHOFYOURAPPLICATION>\\SampleApplication\Web\bin\debug

        </baseDirectory>

                <!--testcontainer: points to the DLL that contains the tests -->

                <!--runconfig: points to solutions testrunconfig that is created by vs.net, list what test to run -->

                <!--resultsfile: normally the test run log is written to the uniquely named testresults directory  -->

                <!--                   this option causes a fixed name copy of the file to be written as well -->

                <buildArgs>                            

        </buildArgs>

                <buildTimeoutSeconds>60</buildTimeoutSeconds>             

      </exec>         

    </tasks>

        <!--Publishers will be done after the build has completed-->

        <publishers>

            <buildpublisher>

                <sourceDir>

          <PATHOFYOURAPPLICATION>\\SampleApplication\Web\

        </sourceDir>

                <publishDir>

          <PATHOFYOURAPPLICATION>\\Sample Application 9091

        </publishDir>

                <useLabelSubDirectory>false</useLabelSubDirectory>

                <alwaysPublish>false</alwaysPublish>

             

      </buildpublisher>

            <merge>

                <files>

                    <file action="Merge" deleteAfterMerge="true">msbuild-results.xml</file>

                    <file action="Merge" deleteAfterMerge="true">

            <PATHOFYOURAPPLICATION>\\SampleApplication\Web\bin\Debug\testResults.trx

          </file>

                 

        </files>

             

      </merge>

            <xmllogger/>

            <email from="[email protected]" mailhost="smtp.XXXX.com" mailport="25" useSSL="FALSE" mailhostUsername=" [email protected]" includeDetails="TRUE" mailhostPassword="XXXX" >

                <users>

                    <user name="Abhishek" group="buildmaster" address=" [email protected]" />

                    <user name="Devs" group="developers" address=" [email protected]" />                 

               </users>

                <groups>

                <group name="developers">

                <notifications>

                <notificationType>Failed</notificationType>                         

            </notifications>                     

          </group>

                    <group name="buildmaster">

                    <notifications>

                    <notificationType>Always</notificationType>                         

            </notifications>                     

          </group>                 

        </groups>             

      </email>         

    </publishers>

        <modificationDelaySeconds>0</modificationDelaySeconds>     

  </project>

</cruisecontrol>

  
Once we are done with the configurations we need to start the CruiseControl.Net Server. For starting the server open Services.msc ->CruiseControl.Net Server. Start this service.



As soon as you are done with that you are ready with your entire configuration to produce automated builds. Access the URL: http://localhost:8080/ViewFarmReport.aspx  and you will see the project that you configured on this dashboard.



From here you can force a build and can also check the status of various builds along with the exception details or the error details if any.
 
As I mentioned earlier you can also download CCTray from this page by clicking on the link "Download CCTray". It will help one to see when the error occurred and by looking into it one is immediately notified for the error in the check-in and can resolve it on the fly.