Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Windows & Linux
Description
I ran into trouble creating a parser class for a multi-line warning.
In the new parser, I set the 'Regular Expression' field to the
following...
(?dm)Warning-(.)\r\n(.),\s*(\d+)
Where in the 'Mapping Script' field, I set matcher.group(1) to the
warning message on the first line of the warning, matcher.group(3) is
the line number and matcher.group(2) is the filename on the second
line of the warning message.
The '\r\n' characters in the 'Regular Expression' field are not
working. Can you please let me know the correct syntax for the regex
of a multiline warning?
Example warning message below:
Warning-[UII-L] Interface not instantiated
/projects/caladan/hudson/jobs/caladan/workspace/caladan/dv/env/xactor/
include/IPZBit.svh, 9
Attachments
Activity
I see, seems the the UI could be improved. Maybe I can check if the match contains a newline, then I can set the property automatically. I currently need to distinguish single and multi-line parsing since the multi-line parser is quite slow (and memory inefficient).
Integrated in 
Hudson Plug-ins (Compile) #92
JENKINS-8399 Removed multi-line checkbox and evaluate the value from the regular expression.
Integrated in Hudson Plug-ins (Compile) #93
JENKINS-8399 Check for
n rather than \n when evaluating the multi line support.
Integrated in Hudson Plug-ins (Compile) #94
JENKINS-8399 Improved documentation.
Ulli, I missed that checkbox. I expected this to be an implicit setting.
After checking it, my multiline warning is found and my test result for you is PASS. Thankyou for fixing this!