Have Geek Brain

Better reporting for CruiseControl.NET

Is there a way to generate a good bug report from Cruise Control?

I like to receive the following message in this report.

  • The line number of the file that splits the assembly
  • The name of the developer who committed this file. (This should not be related to the last person to commit, because the build may be broken earlier than the last person's registration.)

Thanks.

+2


a source to share


3 answers


this should be done with a little xsl parsing :-)
Necessary steps:



  • Create an xsl file (for example, for a blame .xsl)
    this xsl has to look at the <changes / "> node and <msbuild /"> node to get the data.
  • Define a new xslReportBuildPlugin in your webdashboard.config pointing to the new xsl file. Something like this:
        <xslReportBuildPlugin description = "Blame" actionName = "BlameBuildReport" xslFileName = "xsl \ blame.xsl" / ">

  • do iisreset to activate it (just make sure) and clear your browser cache

    now you should see Blame in every build report :-)

+3


a source


Information on creating a custom report

Custom xsl modification to push the error information to the top of the file - this would be helpful when applying the blame



Then, if you add the answers to these questions from Williams' answer, you get information about wine.

+1


a source


  • You already have a file / line number. CruiseControl.NET provides a detailed MSBuild report which is nothing more than a regular compiler output.
  • This is only possible with an extension specific to your version control system. You will have to write such an extension yourself (but I doubt it is worth the effort ...).

NTN.

0


a source






More articles:


All Articles