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
anthonyjeffery
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
anthonyjeffery
added a comment - On the manage hudson page, there is a "Example Log Message" field which I found very useful but not for multiline warnings. As part of this feature request, please make the "Example Log Message" field a multiline/text area field as well. Thankyou, Anthony
anthonyjeffery
added a comment - On the manage hudson page, there is a "Example Log Message" field which I found very useful but not for multiline warnings. As part of this feature request, please make the "Example Log Message" field a multiline/text area field as well. Thankyou, Anthony Good point, thanks. I haven't yet implemented the UI but will consider that. When I have a running version I let you know then you can test this feature before public release.
Integrated in 
Hudson Plug-ins (Compile) #83
JENKINS-8399 Added UI to specify multi-line parsers.
Integrated in Hudson Plug-ins (Compile) #84
JENKINS-8399 Fixed validation of multi-line example.
Can you please install the warnings.hpi and analysis-core.hpi file and test the new feature before I'm making a public release?
See: http://faktorlogik.de:8081/job/Hudson%20Plug-ins%20%28Compile%29/
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
anthonyjeffery
added a comment - I downloaded the new .hpi's and tested to find that the multiline plugin is not being reported in the job even though I successfully tested the muliline warning message on the manage page (manage page screenshot and full log compressed attached). Steps to test for me are to setup a job that prints the warnings in the job log, test the new parser and add it to the job config. I am running base Hudson ver. 1.389
anthonyjeffery
added a comment - I downloaded the new .hpi's and tested to find that the multiline plugin is not being reported in the job even though I successfully tested the muliline warning message on the manage page (manage page screenshot and full log compressed attached). Steps to test for me are to setup a job that prints the warnings in the job log, test the new parser and add it to the job config. I am running base Hudson ver. 1.389 anthonyjeffery
added a comment - Failed test report artifacts anthonyjeffery
made changes -
| Attachment | consoleFull.zip [ 20137 ] | |
| Attachment | verilog2_manageScreenshot.JPG [ 20138 ] |
Sorry about that. I should have tested that in my builds first. Thanks for testing anyway.
Seems still something missing...
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
Integrated in Hudson Plug-ins (Compile) #85
[FIXED JENKINS-8399] Fixed wrong base class for parser.
[FIXED JENKINS-8399] Added german translation.
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
anthonyjeffery
added a comment - I ran the same test against http://faktorlogik.de:8081/job/Hudson%20Plug-ins%20%28Compile%29/88/
and it failed to find/report the multi-line warning in the job.
anthonyjeffery
added a comment - I ran the same test against http://faktorlogik.de:8081/job/Hudson%20Plug-ins%20%28Compile%29/88/
and it failed to find/report the multi-line warning in the job. Did you check the checkbox multi-line support (it's not checked in the screenshot)?
If yes, can you please provide the Groovy script value so I can create a test case?
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
anthonyjeffery
added a comment - 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!
anthonyjeffery
added a comment - 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! 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).
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
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.
| Workflow | JNJira [ 138509 ] | JNJira + In-Review [ 188030 ] |
Integrated in
Hudson Plug-ins (Compile) #81
JENKINS-8399Added a multi-line dynamic parser class.