{"id":866,"date":"2009-10-14T10:38:55","date_gmt":"2009-10-14T08:38:55","guid":{"rendered":"http:\/\/www.navision-blog.de\/2009\/10\/14\/integrating-a-fake-f-make-build-script-into-cruisecontrol-net\/"},"modified":"2023-01-01T13:05:48","modified_gmt":"2023-01-01T13:05:48","slug":"integrating-a-fake-f-make-build-script-into-cruisecontrol-net","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2009\/10\/14\/integrating-a-fake-f-make-build-script-into-cruisecontrol-net\/","title":{"rendered":"Integrating a “FAKE – F# Make” build script into CruiseControl.NET"},"content":{"rendered":"

Since version 0.12 the FAKE build system<\/a> provides an easy way to setup build configurations for CruiseControl.NET<\/a>.<\/p>\n

\n

\u201cCruiseControl.NET<\/strong> is an Automated Continuous Integration server, implemented using the Microsoft .NET Framework.\u201d<\/p>\n

[thoughtworks.org<\/a>] <\/p>\n<\/blockquote>\n

In this article I will show you how you can set up a FAKE build script in CruiseControl.NET. We will use the CalculatorSample which you can download from the FAKE Download page<\/a>.<\/p>\n

If you want to know how this build script works and how you could create one for your own projects please read the \u201cGetting started with FAKE\u201d-tutorial<\/a>.<\/p>\n

If you want to set up \u201cFAKE \u2013 F# Make\u201d build configurations in TeamCity please read \u201cIntegrating a "FAKE \u2013 F# Make" build script into TeamCity<\/a>\u201d.<\/p>\n

Installing CruiseControl.NET<\/h5>\n

You can download CruiseControl.NET from thoughtworks.org<\/a>. After the installation process (further instructions<\/a>) you should see an empty dashboard:<\/p>\n

\"CruiseControl.NET<\/a> <\/p>\n

Installing Subversion<\/h5>\n

The CalculatorSample is using Subversion (SVN) for SourceControl<\/a>, so we need to download SVN from subversion.tigris.org<\/a>. I\u2019m using the \u201cWindows MSI installer with the basic win32 binaries\u201d and installed them under \u201cc:\\Program Files (x86)\\Subversion\\\u201d.<\/p>\n

Installing FxCop<\/h5>\n

The CalculatorSample is using FxCop<\/a>, so we need to download<\/a> and install it next.<\/p>\n

\n

\u201cFxCop is an application that analyzes managed code assemblies (code that targets the .NET Framework common language runtime) and reports information about the assemblies, such as possible design, localization, performance, and security improvements. Many of the issues concern violations of the programming and design rules set forth in the Design Guidelines<\/a> for Class Library Developers, which are the Microsoft guidelines for writing robust and easily maintainable code by using the .NET Framework.\u201d<\/p>\n

[MSDN<\/a>]<\/p>\n<\/blockquote>\n

Creating a FAKE Project<\/h5>\n

Now create a new folder for the CalculatorSample sources. I\u2019m using \u201cd:\\Calculator\\<\/strong>\u201d for the rest of the article.<\/p>\n

The next step is to modify the CruiseControl.NET config file (\u201cc:\\Program Files (x86)\\CruiseControl.NET\\server\\ccnet.config\u201d on my machine):<\/p>\n

\n

<<\/span>cruisecontrol<\/span>><\/span><\/p>\n

  <<\/span>project<\/span>><\/span><\/p>\n

    <<\/span>name<\/span>><\/span>CalculatorExample<\/<\/span>name<\/span>><\/span><\/p>\n

    <<\/span>triggers<\/span>><\/span><\/p>\n

       <<\/span>intervalTrigger<\/span> <\/span>name<\/span>=<\/span>"continuous<\/span>" <\/span>seconds<\/span>=<\/span>"30<\/span>" <\/span>initialSeconds<\/span>=<\/span>"30<\/span>"\/><\/span><\/p>\n

    <\/<\/span>triggers<\/span>><\/span><\/p>\n

    <<\/span>sourcecontrol<\/span> <\/span>type<\/span>=<\/span>"svn<\/span>"><\/span><\/p>\n

      <<\/span>executable<\/span>><\/span>c:\\Program Files (x86)\\Subversion\\bin\\svn.exe<\/<\/span>executable<\/span>><\/span><\/p>\n

      <<\/span>workingDirectory<\/span>><\/span>d:\\Calculator\\<\/<\/span>workingDirectory<\/span>><\/span><\/p>\n

      <<\/span>trunkUrl<\/span>><\/span>http:\/\/fake.googlecode.com\/svn\/trunk\/Samples\/Calculator\/<\/<\/span>trunkUrl<\/span>><\/span><\/p>\n

    <\/<\/span>sourcecontrol<\/span>>    <\/span><\/p>\n

    <<\/span>tasks<\/span>><\/span><\/p>\n

      <<\/span>exec<\/span>><\/span><\/p>\n

        <<\/span>executable<\/span>><\/span>d:\\Calculator\\tools\\Fake\\Fake.exe<\/<\/span>executable<\/span>><\/span><\/p>\n

        <<\/span>baseDirectory<\/span>><\/span>d:\\Calculator\\<\/<\/span>baseDirectory<\/span>><\/span><\/p>\n

        <<\/span>buildArgs<\/span>><\/span>completeBuild.fsx<\/<\/span>buildArgs<\/span>><\/span><\/p>\n

      <\/<\/span>exec<\/span>><\/span><\/p>\n

    <\/<\/span>tasks<\/span>><\/span><\/p>\n

    <<\/span>publishers<\/span>><\/span><\/p>\n

      <<\/span>merge<\/span>><\/span><\/p>\n

        <<\/span>files<\/span>><\/span><\/p>\n

          <<\/span>file<\/span>><\/span>d:\\Calculator\\test\\FXCopResults.xml<\/<\/span>file<\/span>><\/span><\/p>\n

          <<\/span>file<\/span>><\/span>d:\\Calculator\\test\\TestResults.xml<\/<\/span>file<\/span>><\/span><\/p>\n

          <<\/span>file<\/span>><\/span>d:\\Calculator\\output\\Results.xml<\/<\/span>file<\/span>><\/span><\/p>\n

        <\/<\/span>files<\/span>><\/span><\/p>\n

      <\/<\/span>merge<\/span>><\/span><\/p>\n

      <<\/span>xmllogger<\/span> \/><\/span><\/p>\n

    <\/<\/span>publishers<\/span>><\/span><\/p>\n

  <\/<\/span>project<\/span>><\/span><\/p>\n

<\/<\/span>cruisecontrol<\/span>><\/span><\/p>\n<\/p>\n<\/div>\n

In this configuration I set up a trigger which checks every 30 sec. for changes in my CalculatorSample project. <\/p>\n

If SVN finds changes FAKE.exe is called with my build script (completeBuild.fsx). <\/p>\n

After the build I want to merge the FxCop and NUnit output files with my build results to create a build report.<\/p>\n

Configuring the dashboard<\/h5>\n

In order to provide a nicer output on the dashboard we need to modify the BuildPlugins section in the dashboard.config file (\u201cc:\\Program Files (x86)\\CruiseControl.NET\\webdashboard\\dashboard.config\u201d on my machine):<\/p>\n

\n

<<\/span>buildPlugins<\/span>><\/span><\/p>\n

  <<\/span>buildReportBuildPlugin<\/span>><\/span><\/p>\n

    <<\/span>xslFileNames<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\header.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\modifications.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\NCoverSummary.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\fxcop-summary_1_36.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\unittests.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

      <<\/span>xslFile<\/span>><\/span>xsl\\nant.xsl<\/<\/span>xslFile<\/span>><\/span><\/p>\n

    <\/<\/span>xslFileNames<\/span>><\/span><\/p>\n

  <\/<\/span>buildReportBuildPlugin<\/span>><\/span><\/p>\n

  <<\/span>buildLogBuildPlugin<\/span> \/><\/span><\/p>\n

  <<\/span>xslReportBuildPlugin<\/span> <\/span><\/p>\n

     <\/span>description<\/span>=<\/span>"NCover Report<\/span>" <\/span><\/p>\n

     <\/span>actionName<\/span>=<\/span>"NCoverBuildReport<\/span>" <\/span><\/p>\n

     <\/span>xslFileName<\/span>=<\/span>"xsl\\NCover.xsl<\/span>"><\/<\/span>xslReportBuildPlugin<\/span>><\/span><\/p>\n

  <<\/span>xslReportBuildPlugin<\/span> <\/span>description<\/span>=<\/span>"FxCop Report<\/span>"<\/p>\n

     <\/span>actionName<\/span>=<\/span>"FxCopBuildReport<\/span>"<\/p>\n

     <\/span>xslFileName<\/span>=<\/span>"xsl\\fxcop-report_1_36.xsl<\/span>" \/><\/span><\/p>\n

  <<\/span>xslReportBuildPlugin<\/span> <\/span>description<\/span>=<\/span>"NUnit Report<\/span>"<\/p>\n

     <\/span>actionName<\/span>=<\/span>"NUnitBuildReport<\/span>"<\/p>\n

     <\/span>xslFileName<\/span>=<\/span>"xsl\\tests.xsl<\/span>" \/><\/span><\/p>\n

<\/<\/span>buildPlugins<\/span>><\/span><\/p>\n<\/p>\n<\/div>\n

As you can see we use the nant.xsl to transform the FAKE output to HTML.<\/p>\n

Starting the build<\/h5>\n

Now if everything is configured correctly, you can tell CruiseControl.NET to run your build (press \u201cStart\u201d for your build project on the dashboard):<\/p>\n

\"Press <\/p>\n

Now CruiseControl.NET should use SVN to checkout the CalculatorSample sources and run the build. The output on the project page for build 1 should look like this:<\/p>\n

\"Build<\/a> <\/p>\n

\"Build<\/a> <\/p>\n

You can also inspect the NUnit and FxCop results:<\/p>\n

 \"NUnit<\/a> <\/p>\n

\"FxCop<\/a><\/p>\n

Please feel free to give feedback if you have any problems with this article.<\/p>\n

https:\/\/denmarkapoteke.com<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"

Since version 0.12 the FAKE build system provides an easy way to setup build configurations for CruiseControl.NET. \u201cCruiseControl.NET is an Automated Continuous Integration server, implemented using the Microsoft .NET Framework.\u201d [thoughtworks.org] In this article I will show you how you can set up a FAKE build script in CruiseControl.NET. We will use the CalculatorSample which […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[448,546],"tags":[571,492,570,569,664,545,544],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/866"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=866"}],"version-history":[{"count":6,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/866\/revisions"}],"predecessor-version":[{"id":2046,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/866\/revisions\/2046"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=866"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=866"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=866"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}