Friday, June 22, 2007

CruiseControl.Net... Release 1.3.0 With Integration Queues

Some of you may remember this post from last October about a patch I made for serialising builds in CruiseControl.Net. Owen Rogers was kind enough to give me the "keys to the kingdom" to get this integrated into the main CC.Net branch and as of today it is now officially released in CC.Net 1.3.0.

Having had several pair sessions watching Owen "fly" with Resharper was a great experience - many thanks Owen for the effort in getting the final release out as it can't be easy with new baby and work pressures!

As I said from the very beginning this particular iteration doesn't solve everyone's problems of complex build dependencies, nor was any attempt made to do so. However applying the 80/20 rule it appeared many people were like us with the simpler "this project should never build at the same time as this project" requirement. This implementation should do that just fine with a few bells and whistles such as viewing queue contents, controlling the build order and cancelling pending builds...

We have been using the nightly builds of 1.3 for quite a number of months now and it has proven solid from our experiences with it. There are of course further enhancements that can be made, but in discussion with Owen we froze it as is for people to get started with it and feedback their own thoughts. For instance one addition I would like to see is to identify in the CCTray queue which items are continuous triggers (checking for modifications) versus which are actual builds that will take place. Perhaps a simple "F" stamped into the icon corner for forced builds with additional information being passed in the xml request from the server about the integration request.

Documentation for how to use the integration queue feature is here.


At August 03, 2007 7:33 AM, Anonymous Anonymous said...

hi, im wondering if you can help me with this. im getting this error:
C:\Data\Projects\CInteg\Build Automation\EquityServices\Release 22\Scripts\NAnt\main.xml(834,4): External Program Failed: C:\Data\Projects\CInteg\NCover1.3.3\NCover.Console.exe (return code was -2146233082)

Fatal execution engine error.

can you tell why is it happening? thanks so much in advance!

At August 03, 2007 8:37 AM, Blogger kiwidude said...

The issue is that you are using NCover 1.3.3. While this is the only option for a machine without .NET 2.0 on it unfortunately it does have a number of bugs. Sometimes you get lucky and it works but other times the code being profiled triggers something within NCOver that causes it to fail with this error.

Install the .NET 2.0 framework on your machine and use the latest NCOver would be my recommendation...

At August 07, 2007 8:52 AM, Anonymous Anonymous said...

yes, im actually running .Net 1.1 Framework, i'm afraid i cant change it yet to .Net 2.0, maybe this error can help:


[exec] NCover.Console v1.3.3 - Code Coverage Analysis for .NET -
[exec] Command: C:\Data\Projects\CInteg\NUnit2.2\bin\nunit-console.exe
[exec] Command Args: TestAccenture.EquityServices.EAExtension.RSU.ActTaxUpl.dll
[exec] Working Directory: C:\Data\Projects\CInteg\Build Automation\EquityServices\Release 22\WorkingDirectory\Source\TestAccenture.EquityServices.EAExtension.RSU.ActTaxUpl\bin
[exec] Assemblies: Accenture.EquityServices.EAExtension.RSU.ActualTaxUpl;Accenture.EquityServices.EAExtension.RSU.Common;Accenture.EquityServices.EAExtension.RSU.ReleaseApp;Accenture.EquityServices.EAExtension.RSU.ReleaseVestUpl;Accenture.EquityServices.EAExtension.Utility;Accenture.EquityServices.EAExtension.Common;Accenture.EquityServices.EAExtension.Data;Accenture.EquityServices.EAExtension.Model;Accenture.EquityServices.EAExtension.Presenter
[exec] Coverage File: C:\Data\Projects\CInteg\Build Automation\EquityServices\Release 22\WorkingDirectory\Output\Coverage\NCover_RSU.ActualTaxUpl.xml
[exec] Coverage Log:
[exec] ******************* Program Output *******************
[exec] NUnit version 2.2.0
[exec] Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov, Charlie Poole.
[exec] Copyright (C) 2000-2003 Philip Craig.
[exec] All Rights Reserved.
[exec] OS Version: Microsoft Windows NT 5.0.2195.0 .NET Version: 1.1.4322.573
[exec] Fatal execution engine error.
[exec] .***************** End Program Output *****************
[exec] Copied 'C:\Data\Projects\CInteg\NCover1.3.3\Coverage.xsl' to 'C:\Data\Projects\CInteg\Build Automation\EquityServices\Release 22\WorkingDirectory\Output\Coverage\Coverage.xsl'
[exec] C:\Data\Projects\CInteg\Build Automation\EquityServices\Release 22\Scripts\NAnt\main.xml(834,4): External Program Failed: C:\Data\Projects\CInteg\NCover1.3.3\NCover.Console.exe (return code was -2146233082)

do you think NUnit has something to do with this?

At August 07, 2007 10:42 PM, Blogger kiwidude said...

I honestly have no idea what the underlying bug in NCover 1.3.3 is - only Peter Waldschmidt may know the answer to that. You pretty much have no options at this point - further code churn on the codebase may cause it to "come right" again at some point.


Post a Comment

Links to this post:

Create a Link

<< Home