Craig your xml is very clean and easy to read however I can't find an ncoverexplorer task/block. CCNET gives me an exception and there are no docs for it. Is this possibly part of the snazzy new 1.5 stuff?
Cheers Mark On Thu, May 28, 2009 at 4:48 PM, Craig & Sammi Sutherland < [email protected]> wrote: > Ok, I have some more bad news then – the work in 1.5.0 is for nCover 3.0. > We did some joint work together with them (they bribed us with a couple of > licenses ;-) > > > > I’ll need some time to look into this for you – but I’ll need some time so > it might not be until after the week-end. > > > > For some quick pointers, here is what I remember: > > · For nUnit – it produces an XML results file (this may need to be > specified in the command-line args). This file needs to be merged (using the > merge task) in order for the results to appear in the dashboard. > > · The configuration for displaying nCover results needs to be > configured in dashboard.config – this uses an XSL-T file and the XML file > from the nCover task. > > · The dashboard caches its configuration settings – if you change > the config then you’ll need to restart web server to see any changes. > > > > I think CC.NET used to use nCover 1.5.8. Here is it’s MSBuild task for > running nCover: > > <target name="test.unit" description="runs unit tests"> > > <property name="unittests.fullpath" value=" > ${path::get-full-path(build.dir)}\unittests" /> > > <exec program="${ncover-console.exe}" workingdir=" > ${unittests.fullpath}" commandline="//reg "..\..\${nunit-console.exe} > " "${unittests.fullpath}\${unittests.dll}" * > /xml:../${unittests.dll}-results.xml* /nologo //w " > ${unittests.fullpath}""/> > > > > <ncoverexplorer program=" > tools\ncoverexplorer\ncoverexplorer.console.exe" projectName="CCNet" > outputDir="${build.dir}" satisfactoryCoverage="80" reportType="4" * > xmlReportName="CoverageSummary.xml"*> > > <fileset> > > <include name="${unittests.fullpath}\coverage.xml"/> > > </fileset> > > </ncoverexplorer> > > </target> > > > > And the merge task for including the results: > > <merge> > > <files> > > <file>*build\*-results.xml*</file> > > <file>build\fxcop\*.xml</file> > > <file>*build\CoverageSummary.xml*</file> > > <file>build\ccnet.results-vil.xml</file> > > </files> > > </merge> > > > > And finally, dashboard.config has the following config: > > <buildPlugins> > > <buildReportBuildPlugin> > > <xslFileNames> > > <!-- Other plug-ins omitted for brevity --> > > <xslFile>xsl\NCoverExplorerSummary.xsl</xslFile> > > </xslFileNames> > > </buildReportBuildPlugin> > > <buildLogBuildPlugin /> > > <!-- Other plug-ins omitted for brevity --> > > <xslReportBuildPlugin description="NCover Report" actionName=" > NCoverBuildReport" xslFileName="xsl\NCoverExplorer.xsl" /> > > </buildPlugins> > > > > I haven’t checked its validity – I need to start work – but it will give > you a starting point if you need it urgently. > > > > Craig > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Mark Levison > *Sent:* Friday, 29 May 2009 8:24 a.m. > *To:* [email protected] > *Subject:* [ccnet-user] Re: I don't understand the section on configuring > CruiseControl to display NCover? > > > > I'm using NCover 1.5.8 - the last "community edition" - trying to explain > to my client why they should by NCover at this stage would cause > unimaginable pain. I can give CCNET 1.5 a spin - is there an installer? How > do I figure out what I need to do in terms of NCover? > > Cheers > Mark > > On Thu, May 28, 2009 at 4:18 PM, Craig & Sammi Sutherland < > [email protected]> wrote: > > Hi Mark, > > > > I’ve just checked on this – it appears that our documentation is a bit out > of date L > > > > First, which version of nCover are you using? If you are using nCover 3 – > they have a good tutorial on their site about integrating with CC.NET: > http://docs.ncover.com/how-to/continuous-integration/cruisecontrol-net/. > > > > If you are using an older version, let me know what and I’ll see if I can > put together something for you. > > > > I should also mention, that in the current version of CC.NET (i.e. 1.4.4) > we don’t support NCover very well, but in the next version (1.5.0) we will > be including out-of-box support for it. So if you’re feeling adventurous, > and don’t mind working with an in-development version, you can try the > latest development release - > http://ccnetlive.thoughtworks.com/CCNet-builds/1.5.0/. > > > > There is some bad news though – because of the way our documentation works, > we can’t start adding documentation for 1.5.0 until 1.4.4 is released L > > > > > > Craig > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Mark Levison > *Sent:* Friday, 29 May 2009 7:57 a.m. > *To:* ccnet-user > *Subject:* [ccnet-user] I don't understand the section on configuring > CruiseControl to display NCover? > > > 1) At this stage I get NCover to run. Excellent and I've add the Merge task > that the docs refer to, but then I'm confused by the section below that > talks about configuring the webdashboard. My web.config file is just the > default from the CCNet install, so I have no examples of the including > plugins (sorry I'm not a web developer by trade). Our dashboard config file > (also the default) already includes ncover related parts - but none of them > are named plugin. The page for each build includes an NCover link - but > nothing appears on that page. > > 2) Also our NUnit results are no longer reported how do fix that? Also can > I do something so that an NUnit failure still fails the build? > > Cheers > Mark > Configuring your Reporting Application to display NCover results > > For displaying the results, CruiseControl.NET *currently supports NCover > 1.3.3*. > > If you are using the Web > Dashboard<http://confluence.public.thoughtworks.org/display/CCNET/Web+Dashboard>, > edit your web.config file and include the > ThoughtWorks.CruiseControl.WebDashboard.Plugins.NCover.NCoverReportBuildPluginBuild > Plugin. > > If you are using [Project Report Web Application], edit your web.configfile > and include the > Coverage.aspx Build Plugin. > > > > Mark Levison - Agile/Lean Transition Coach || > > Agile Editor @ InfoQ <http://www.infoq.com/about.jsp> || > > > > 613-862-2538 (cell) || > > Twitter <http://twitter.com/mlevison> || > > Blog <http://www.notesfromatooluser.com/> Recent Entries: > > > > Acceptance Test Tools for Web > Apps<http://www.notesfromatooluser.com/2009/02/functionalacceptance-test-tools-for-web-apps.html%20>|| > > Do You Suspect You Have a Less than Productive Person on Your > Team?<http://www.notesfromatooluser.com/2009/01/do-you-suspect-you-have-a-less-than-productive-person-on-your-team.html> > > > > > > Mark Levison - Agile/Lean Transition Coach || > > Agile Editor @ InfoQ <http://www.infoq.com/about.jsp> || > > > > 613-862-2538 (cell) || > > Twitter <http://twitter.com/mlevison> || > > Blog <http://www.notesfromatooluser.com/> Recent Entries: > > > > Acceptance Test Tools for Web > Apps<http://www.notesfromatooluser.com/2009/02/functionalacceptance-test-tools-for-web-apps.html%20>|| > > Do You Suspect You Have a Less than Productive Person on Your > Team?<http://www.notesfromatooluser.com/2009/01/do-you-suspect-you-have-a-less-than-productive-person-on-your-team.html> > > > > Mark Levison - Agile/Lean Transition Coach || Agile Editor @ InfoQ<http://www.infoq.com/about.jsp>|| 613-862-2538 (cell) || Twitter <http://twitter.com/mlevison> || Blog<http://www.notesfromatooluser.com/>Recent Entries: Acceptance Test Tools for Web Apps<http://www.notesfromatooluser.com/2009/02/functionalacceptance-test-tools-for-web-apps.html%20>|| Do You Suspect You Have a Less than Productive Person on Your Team?<http://www.notesfromatooluser.com/2009/01/do-you-suspect-you-have-a-less-than-productive-person-on-your-team.html>
