Build 1937 - MSBuild log

Continua CI Bugs
1

I've got a number of issues with the way Continua logs MS Build stage actions.

Firstly, when I review the output of MSBuild (2.x) in Continua it seems to be truncating the exception message being returned. (see ***ci/builds/log/{GUID})

For instance I had a MSBuild failure that should have read.

".....(REMOVED)...Security.Nunit.vbproj(138,11): error MSB4019: The imported project "C:\Microsoft.VisualBasic.targets" was not found. Confirm that the path in the
declaration is correct, and that the file exists on disk"

But only had the following. Looks like a simple string length truncation.

".....(REMOVED)...Security.Nunit.vbproj(138"

Secondly, it looks like some of the parameters for the output are not correctly handling the last backslash for a folder or there is an error in the formatting for the log parameters.

Attachment unavailable

2

Hi Jamie

The truncation issue is actully not a truncation issue, it’s a formatting issue in our custom msbuild logger which formats the output so that continua understand it, the logger is not escaping commas where it should be. We should have a new build out later today. The double backslash is actually required, here’s the comment in our code where this is done :


// Any property values that end with a \ needs to be replaced with \ otherwise MSBuild interprets this as an
// escaped quote which causes all sorts of problems