I’m using CCNet 1.1 with the FB plugin, but the web dashboard doesn’t seem to understand the FB logs. I export the log as the last step of the build and then merge it during the publishing stage, so it’s part of the complete build log, but errors don’t seem to be listed. Has anyone made a dashboard extension which could be used for this, or is it already there and I have just missed it somehow?
Cheers,
/axl
Hi Andreas,
Have you checked the exported XML from FinalBuilder? Are all the actions exporting OK at that point?
Regards,
Angus
Well, I export the log with the default settings and it looks ok. It just doesn’t seem like the CCNet Dashboard understands the log format. If an FB task fails, there is nothing in the summary, the only way to see the output is via the “View Build Log” menu item.
Normally one has to add plug-ins in the Dashboard for each type of log, like NUnit, Simian, MsBuild, etc. but I didn’t find any for FB logs. Have I installed it incorrectly perhaps?
cheers,
/axl
Hi Andreas,
At the moment we’re not doing anything special for FB log output into CC.NET. It just adds the output from FBCMD as plain text.
I’ll look into whether or not we can make a Publisher plugin to format XML logs from FinalBuilder.
- Angus
I don’t think you need to format the FB output differently, but you may need to write an additional xsl transform that can extract the vital information from the FB log. It would be part of the CCNet plugin installation. It would then be added to the dashboard.config file, or be an extension of the existing compile.xsl transform. I’ll experiment with it to see if I can come up with an example.
How do people use the FB integration with CCNet on other sites? Have you written your own transforms or do you just browse the build log if there’s a failure?
/axl
Andreas,
Well, at the moment you’re exporting the XML log from FinalBuilder yourself… something that we have the benefit of being able to do is automate the entire process so you don’t have to add any actions to your build process. ;-). I’ll see what we can do.
In the meantime, text output (and logging into the build server to manually browse the build log) is probably the easiest option, if not the most functional.
Regards,
Angus
Ok, no problem. At least I know I’m not missing out on something existing.
cheers,
/axl
Any news on that front? I’m having the same problem, and it’s EXTREMELY annoying.
Thanks,
Omer.
Hi Omer,
Do you mean you’re having a problem exporting logs as XML, or you’re having a problem exporting the XML logs in a format which can be used by the CruiseControl.NET dashboard?
Regards,
Angus
I can’t speak for Omer, but as for myself, I would find an XSL transformation for the FinalBuilder logs very Helpful.
Hi guys,
We'll investigate a turnkey solution for XML logs soon. In the meantime, I'm going to attach some XSL that another user has been using for XML log exporting. He isn't exporting to the Web Dashboard itself (just to emails), but it should give you some idea of what's possible.
The idea is to use the "Export Log" action inside FinalBuilder to export the FB log to an XML file, and then use that XML file as input to CruiseControl.NET.
Quote:
In the
ccservice.exe.config or ccnet.exe.confg, there's an xslFiles node. Add
a path to the finalbuilder.xsl there. Then in an FB script export the
log to xml (mine only exports error actions). Lastly in the
ccnet.config publishers node, you need:
(merge)
(files)
(file_c:\fblogs\fblog.xml(/file)
(/files)
(/merge)
This must come before the xmlLogger.
NB: Please replace the parentheses with angle brackets, due to our annoying forum software.finalbuilderxsl.zip (1.638 KB)
The xsl needed some tweaking to work with FB5, and does not look quite as good as the HTML export of FB, but I guess it’ll do for now.
This is a short sample of how to integrate FinalBuilder into CruiseControl.Net
It was used for testing, not yet in an live situation. The xsl code is old, and not optimized, and intended for FB4. The above xsl has much better code.
In this testproject, all the actions (like FxCop, NUnit/NCover, …) write their own log as xml to files named ?-results.xml.
The FinalBuilder 4 script has an Export log action in the Main and in the Failure actionlist. It saves the log as xml to Fblog.xml
These names can be found (and changed) in the ccnet.config file.
This project uses the CruiseControl 1.1 plugin for finalbuilder. In version 1.3, the plugin is standard, and maybe the working will be changed?
For debugging:
- Start the CruiseControl server in debug mode.
- Start the server not as a service, but from the commandline
- Do not use the FinalBuilder plugin, but use an executable call with an extra /L text logging option to see errors that fail FinalBuilder before the export log action is reached.
If you have any questions, or improvements (yes please!), or need the full example, use the FB forums. Or mail me: (address in readme)
Hi Jaap,
Thanks for posting this. I just wanted to confirm that the plugin coming in CC.Net 1.3 (not a final release yet) has the same syntax/functionality as the previous plugin versions.
Regards,
Angus