[JIRA] (JENKINS-57365) MsBuildParser reports warnings if the build project contains "info"

stephan.senkbeil@sonoware.de (JIRA)

unread,

May 8, 2019, 3:07:04 AM5/8/19

to jenkinsc...@googlegroups.com

Stephan Senkbeil created an issue

Jenkins /

JENKINS-57365

MsBuildParser reports warnings if the build project contains "info"

Issue Type:	Bug
Assignee:	Ulli Hafner
Components:	analysis-model
Created:	2019-05-08 07:06
Environment:	Jenkins 2.176 Analysis Model API Plug-in 5.0.0 Warnings Next Generation Plugin 5.0.0
Priority:	Minor
Reporter:	Stephan Senkbeil

The warning analysis reports a false positive if e.g. the build project name contains the string "info".

For example, the line below is matched by the regexp parser:

 
                                                                311>------ Build started: Project: sysinfo, Configuration: Debug Win32 ------ 
                                                            

This obviously leads to an error during the report generation:

 
                                                                [DEBUG] [-ERROR-] Can't resolve absolute paths for some files:
[DEBUG] [-ERROR-] - C:/jenkins/workspace/acecode-win/build/------ Build started: Project
[DEBUG] [-ERROR-] Can't create fingerprints for some files:
[DEBUG] [-ERROR-] - 'C:/jenkins/workspace/acecode-win/build/------ Build started: Project', IO exception has been thrown: java.nio.file.InvalidPathException: Illegal char <:> at index 59: C:/jenkins/workspace/acecode-win/build/------ Build started: Project

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ullrich.hafner@gmail.com (JIRA)

unread,

May 8, 2019, 8:29:02 AM5/8/19

to jenkinsc...@googlegroups.com

Ulli Hafner assigned an issue to Unassigned

Jenkins /

JENKINS-57365

MsBuildParser reports warnings if the build project contains "info"

Change By:	Ulli Hafner
Labels:	help-wanted newbie-friendly
Assignee:	Ulli Hafner

Add Comment

stephan.senkbeil@sonoware.de (JIRA)

unread,

May 8, 2019, 9:09:02 AM5/8/19

to jenkinsc...@googlegroups.com

Stephan Senkbeil commented on

JENKINS-57365

Re: MsBuildParser reports warnings if the build project contains "info"

I don't know about the broader scope of the different versions of MsBuild and the corresponding outputs that have to be matched with the regexp, but I have a suggestions which fixes my issue. Obviously I cannot guarantee that this doesn't break anything else but looking at the examples in the unit test file msbuild.txt it could be valid.

New regexp pattern:

 
                                                                MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"
            + ANT_TASK + "(?:(?:\\s*(?:\\d+|\\d+:\\d+)>)?(?:(?:(?:(.*?)\\((\\d*)(?:,(\\d+))?[a-zA-Z]*?\\)|.*LINK)\\s*:|"
            + "(.*):)\\s*([A-z-_]*\\s(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))[^A-Za-z0-9]\\s*:?\\s*([A-Za-z0-9\\-_]+)?"
            + "\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/\\\\][^\\]\\\\]+\\])?"
            + "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";
 
                                                            

I removed the "optional"-flag (question mark) for the whitespace before the note/info/warning/fatal error strings. In other words, the strings are now only matched if they have a whitespace right before them which seems to be valid for the test cases in the unit test file msbuild.txt.

This should probably be checked by someone more familiar with the various MsBuild outputs but I just wanted to contribute a bit and provide some guidance to solve the issue.