Yes, it should work on Visual Studio messages, too. Please file a new bug
report, it should be quite easy to fix.
Ulli
Am Samstag, 19. Oktober 2013 schrieb Mike Hambidge :
> Does anyone know if the MSBuild parser for the Warnings Plugin is supposed
> to detection Visual Studio Code Analysis warnings? The reason I ask is that
> I've encountered a problem where the console output for code analysis
> warnings contains an extra space character that causes the regex used
> within the MSBuild parser to not match.
>
> Typically, the various warnings from MSBuild (actual msbuild warnings,
> StyleCop warnings, etc) include text in the format:
>
> ... warning: <ID>: Message
>
> Where ID is something like "SA1234" for a StyleCop warnings. But the
> Visual Studio Code Analysis output has an extra space after the <ID>, so
> looks like
>
> ... warning: CA1234 : Message
>
> I suppose I may be encountering a bug, but before creating a bug report I
> was trying to see if the MSBuild parser was even intended to catch the code
> analysis warnings.
>
> Thanks gang.
>
> - Mike
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com <javascript:_e({},
> 'cvml', 'jenkinsci-users%2bunsubscr...@googlegroups.com');>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
