Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8399

Request for Support of multi-line warnings in user defined Warnings Parser

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • warnings-plugin
    • 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 anthonyjeffery created issue -
          drulli Ulli Hafner made changes -
          Field Original Value New Value
          Priority Major [ 3 ] Minor [ 4 ]
          drulli Ulli Hafner made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #81
          JENKINS-8399 Added a multi-line dynamic parser class.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #81 JENKINS-8399 Added a multi-line dynamic parser class.

          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 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
          drulli Ulli Hafner added a comment -

          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.

          drulli Ulli Hafner added a comment - 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.
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #83
          JENKINS-8399 Added UI to specify multi-line parsers.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #83 JENKINS-8399 Added UI to specify multi-line parsers.
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #84
          JENKINS-8399 Fixed validation of multi-line example.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #84 JENKINS-8399 Fixed validation of multi-line example.
          drulli Ulli Hafner added a comment -

          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/

          drulli Ulli Hafner added a comment - 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/
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]

          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 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

          Failed test report artifacts

          anthonyjeffery anthonyjeffery added a comment - Failed test report artifacts
          anthonyjeffery anthonyjeffery made changes -
          Attachment consoleFull.zip [ 20137 ]
          Attachment verilog2_manageScreenshot.JPG [ 20138 ]
          drulli Ulli Hafner added a comment -

          Sorry about that. I should have tested that in my builds first. Thanks for testing anyway.

          Seems still something missing...

          drulli Ulli Hafner added a comment - Sorry about that. I should have tested that in my builds first. Thanks for testing anyway. Seems still something missing...
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #85
          [FIXED JENKINS-8399] Fixed wrong base class for parser.
          [FIXED JENKINS-8399] Added german translation.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #85 [FIXED JENKINS-8399] Fixed wrong base class for parser. [FIXED JENKINS-8399] Added german translation.
          drulli Ulli Hafner added a comment -

          Ok, now verified on this build machine. Can you please retry?

          drulli Ulli Hafner added a comment - Ok, now verified on this build machine. Can you please retry?
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]

          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 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.
          drulli Ulli Hafner added a comment - - edited

          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?

          drulli Ulli Hafner added a comment - - edited 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?
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]

          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 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!
          drulli Ulli Hafner added a comment -

          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).

          drulli Ulli Hafner added a comment - 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).
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #92
          JENKINS-8399 Removed multi-line checkbox and evaluate the value from the regular expression.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #92 JENKINS-8399 Removed multi-line checkbox and evaluate the value from the regular expression.
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #93
          JENKINS-8399 Check for
          n rather than \n when evaluating the multi line support.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #93 JENKINS-8399 Check for n rather than \n when evaluating the multi line support.
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #94
          JENKINS-8399 Improved documentation.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #94 JENKINS-8399 Improved documentation.
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 138509 ] JNJira + In-Review [ 188030 ]

          People

            drulli Ulli Hafner
            anthonyjeffery anthonyjeffery
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: