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

Enhance plugin to capture and report errors like it does warnings

    Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: warnings-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.532.3 Warnings Plugin 4.40
    • Similar Issues:
    • Released As:
      5.0.0-beta3

      Description

      Add the ability to have Errors reported by the plugin.
      Having the ability to have the Errors reported like the Warnings would be very useful.
      Currently some parsers may report errors but they are still listed as Warnings which is confusing to users who view the reports.
      The simplest solution I think would be to just have users have to make their own parsers and then a flag to indicate if the type the parser is looking for is Warnings or Errors which would then modify the reports to says "Warnings" or "Errors" in all the appropriate places.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Can you please add some more details (UI sketch, etc.) on how this should be presented to the user? Currently one result block is shown in the UI for each parser. Should the errors be shown within the existing blocks? Or should there be one error block for all parsers? Or one error block for each parser?

          Show
          drulli Ulli Hafner added a comment - Can you please add some more details (UI sketch, etc.) on how this should be presented to the user? Currently one result block is shown in the UI for each parser. Should the errors be shown within the existing blocks? Or should there be one error block for all parsers? Or one error block for each parser?
          Hide
          macdrega Joerg Schwaerzler added a comment - - edited

          Great to see that I'm not the only one thinking about an enhancement like this for the warnings plugin.
          Currently any errors are reported as warnings which is very confusing for many developers. In addition, in case the build is broken (=red) no parsing will be done, the errors will not be reported correctly. As a workaround each msbuild has to be configured to continue even in the case of a build error so the warnings plugin later on can report the errors.
          Parsing the compiler errors currently has even higher priority to us than parsing the warnings. However this plugin looks very promising - if only we could avoid confusing the developers about errors reported as warnings.
          We're currently using following version(s):
          Warnings v4.48
          Maven-plugin v2.11
          Analysis-core v1.75
          Matrix-project v1.6
          Token-macro v1.10

          Show
          macdrega Joerg Schwaerzler added a comment - - edited Great to see that I'm not the only one thinking about an enhancement like this for the warnings plugin. Currently any errors are reported as warnings which is very confusing for many developers. In addition, in case the build is broken (=red) no parsing will be done, the errors will not be reported correctly. As a workaround each msbuild has to be configured to continue even in the case of a build error so the warnings plugin later on can report the errors. Parsing the compiler errors currently has even higher priority to us than parsing the warnings. However this plugin looks very promising - if only we could avoid confusing the developers about errors reported as warnings. We're currently using following version(s): Warnings v4.48 Maven-plugin v2.11 Analysis-core v1.75 Matrix-project v1.6 Token-macro v1.10
          Hide
          drulli Ulli Hafner added a comment -

          You can already activate the configuration option to start the warnings parser even if the build is red.

          While the changes for the parsers are obvious, the UI side of this feature request still needs to be discussed. Do you have any suggestions?

          Show
          drulli Ulli Hafner added a comment - You can already activate the configuration option to start the warnings parser even if the build is red. While the changes for the parsers are obvious, the UI side of this feature request still needs to be discussed. Do you have any suggestions?
          Hide
          macdrega Joerg Schwaerzler added a comment -

          Thanks for the note about the switch to always run the analysis. Didn't notice that one

          About the UI changes:
          Unfortunately I don't know the details on how the warnings plugin displays all those warnings.
          Probably 'Warning(s)' could be renamed into something more generic like 'Issue(s)' or 'Finding(s)'. This change probably won't take much time.

          Show
          macdrega Joerg Schwaerzler added a comment - Thanks for the note about the switch to always run the analysis. Didn't notice that one About the UI changes: Unfortunately I don't know the details on how the warnings plugin displays all those warnings. Probably ' Warning(s) ' could be renamed into something more generic like ' Issue(s) ' or ' Finding(s) '. This change probably won't take much time.
          Hide
          drulli Ulli Hafner added a comment -

          The new parser API has support for errors as well. What still need to be implemented: special handling in the user interface.

          Show
          drulli Ulli Hafner added a comment - The new parser API has support for errors as well. What still need to be implemented: special handling in the user interface.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              jstarbird Jon Starbird
            • Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: