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

Warnings contain no filename

XMLWordPrintable

    • 5.0.0-beta3

      Since upgrading warnings plugin to 4.63 my console logs are spamed with output like this: https://gist.github.com/jakub-bochenski/18a989b192642664f549f36995c5dd06

      Can this be removed, why does it even happen?

          [JENKINS-47268] Warnings contain no filename

          Jakub Bochenski created issue -
          Jakub Bochenski made changes -
          Link New: This issue relates to JENKINS-6748 [ JENKINS-6748 ]
          Jakub Bochenski made changes -
          Link New: This issue relates to JENKINS-47269 [ JENKINS-47269 ]

          Ulli Hafner added a comment - - edited

          You can disable logging output of all static analysis tools (Jenkins global configuration).

          Ulli Hafner added a comment - - edited You can disable logging output of all static analysis tools (Jenkins global configuration).
          Ulli Hafner made changes -
          Component/s Original: checkstyle-plugin [ 15512 ]
          Component/s Original: warnings-plugin [ 15513 ]
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Jakub Bochenski made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Ulli Hafner added a comment -

          What parser are you using? Any idea why your filename in the warnings is only whitespace?

          Ulli Hafner added a comment - What parser are you using? Any idea why your filename in the warnings is only whitespace?
          Ulli Hafner made changes -
          Summary Original: GitBlamer spams console with over 1K lines New: Warnings contain no filename

          Jakub Bochenski added a comment -

          drulli I'm using Warnings plugin with Maven parser, as seen in the snippet 

          [WARNINGS] Parsing warnings in console log with parser Maven

          > Any idea why your filename in the warnings is only whitespace?
          Not really.
          This happens in most (if not all) of our Maven builds that use the parser
          This happens both in projects that checkout the repo directly to $WORKSPACE and in projects that use the "Check out to a subdirectory" option.

          Jakub Bochenski added a comment - drulli I'm using Warnings plugin with Maven parser, as seen in the snippet [WARNINGS] Parsing warnings in console log with parser Maven > Any idea why your filename in the warnings is only whitespace? Not really. This happens in most (if not all) of our Maven builds that use the parser This happens both in projects that checkout the repo directly to $WORKSPACE and in projects that use the "Check out to a subdirectory" option.

          Ulli Hafner added a comment -

          I see, seems that I forgot that there might be warnings without a filename.

          Ulli Hafner added a comment - I see, seems that I forgot that there might be warnings without a filename.

            drulli Ulli Hafner
            jbochenski Jakub Bochenski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: