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

Warnings from parallel build stages are always aggregated

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Duplicate
    • warnings-ng-plugin
    • None
    • Jenkins ver. 2.121.3
      Warnings NG Plugin: 5.1.0

    Description

      When using the clang tool for parsing warnings in the console of a parallel pipeline (10 build stages which all generate warnings) the number of warnings are always summed up. It seems that the stage scans always the full console at the point of execution.

      Note: I am using a scripted pipeline.

      Is this a known issue or am I doing something wrong?

      Example code (project_x / project_x_name is different for every parallel stage):

      def clangIssues= scanForIssues id: "${project_x}", name: "${project_x_name}",  tool: clang(id: "project_x", name: "project_x_name"), aggregateResults: false
      publishIssues: issues: [clangIssues], id: "${project_x}", name: "${project_x_name}"

      Attachments

        Issue Links

          Activity

            thefifo Wolfgang Issovits created issue -
            drulli Ulli Hafner made changes -
            Field Original Value New Value
            Link This issue duplicates JENKINS-44450 [ JENKINS-44450 ]
            drulli Ulli Hafner made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            drulli Ulli Hafner made changes -
            Link This issue is duplicated by JENKINS-55258 [ JENKINS-55258 ]

            People

              drulli Ulli Hafner
              thefifo Wolfgang Issovits
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: