Continuous Integration with CodePlex and Cruise Control.Net

Return to previous page

  • 4/7/2015
  • 593 Views

Comments

593 Views

Continuous Integration with CodePlex and Cruise Control.Net

Last updated 6 years ago

Comments

Common

(Enter the content of this article below)

Advanced

 
Its quite simple to setup CI with Cruise Control.Net and CodePlex. All you need to do is use SVN to pull down the latest code using the Exec task as shown below, then build the solution. This example pulls the code from the DNN Automation Tests project. SVNClientPath is the path to the svn.exe on your build server.


<Exec Command="%22$(SVNClientPath)svn%22 checkout https://dotnetnukeautomation.svn.codeplex.com/svn C:\Tests\Source" />

You will probably need to change some config values before you build. To do that you can sue the MSBuild Community Tasks project and use the XmlUpdate task as shown:


<XmlUpdate Namespace="http://schemas.microsoft.com/.NetConfiguration/v2.0"
XmlFileName="$(TestsFolder)\Source\DotNetNuke.Tests.UI.WatiN.BuildVerification\app.config"
Xpath="/configuration/appSettings/add[@key='TestVersion']/@value"
Value="$(BuildVersion)" />

Once you have the code and have done your updates you execute the build as follows.


<MSBuild Projects="$(TestsFolder)\Source\DotNetNuke_WatiN_Tests.sln" Properties="Configuration=Release;Platform=Any CPU" Targets="Rebuild" />


Now just create a CCNet project and call the task that has the above two steps and you're done.

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out