I am working on a quite a large build with very, very verbose logging. This means the log files can become really big. Since the FinalBuilder script is multithread, it can be very complex to analyze the log in the interface of continua itself. However when I click the Download As Plain Text, the command times out. I think the log should always be written to a text file and be available as an artifact (preferably per step).
I found the log here:
C:\Continua\Ws[MyBuild]\43
It is 40 megabytes. Unfortunately it’s a binary file so I cannot read it.
This is something that we are planning to do. The logging is being reworked at the moment (to allow live updating of the log view). What we do here with the finalbuilder logs, is to export them to html in FinalBuilder (use the export log action), and then add a workspace rule to copy the html file to the server, an add a custom report to the configuration : http://wiki.finalbuilder.com/x/agMZ
Great solution, thanks! I can’t wait for the live logging feature 