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

Warning trend graph inconsistent in Pipeline

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: warnings-plugin
    • Labels:
      None
    • Environment:
      warnings-plugin v4.65
    • Similar Issues:
    • Released As:
      5.0.0-beta2

      Description

      I have a pipeline job that parses warnings for several builds, using the same warnings parser. For example, building 32 and 64 bit cmake with gcc, so parsing output for 32 and 64 bit build independently. This results into 2 (in my case more) trend graphs to be visible in the Job view. This happens on the same build node in the same pipeline stage in parallel executions. The warnings trend graphs now mix results of different warnings(...) calls.

      What is totally unclear to me, and I have not found any documentation (while searching for an hour) how warnings calls are assigned to a trend graph, i.e. which call appends the results to which graph? Can somebody clarify how this is done? By node? by stage? or by time order? or something else?

      Another visual problem is, that the trend graph shows the name of the warnings parser only. For example "Doxygen Warnings Trend". When using the same parser multiple times, you see the same name multiple times and it is impossible to know what the graph is really related to. It would be nice to be able to give the trend graph a unique name during the warnings step. Then it would be possible to uniquely assign parsed warnings to the right graph and a user would know what the graph is about.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          This should be covered by the rework of the pipeline support. (It still needs some time until this new features will be available in a release.)

          Show
          drulli Ulli Hafner added a comment - This should be covered by the rework of the pipeline support. (It still needs some time until this new features will be available in a release.)
          Hide
          rs Reinhard S added a comment -

          Is there a workaround for the old system until the new features are available? If I use multiple warnings calls, do I need to do them in the right order to get the warnings assigned to the right trend graph? Something you can recommend?

          Show
          rs Reinhard S added a comment - Is there a workaround for the old system until the new features are available? If I use multiple warnings calls, do I need to do them in the right order to get the warnings assigned to the right trend graph? Something you can recommend?
          Hide
          drulli Ulli Hafner added a comment - - edited

          I'm not aware of a workaround. That is the reason for the whole rework...

          Show
          drulli Ulli Hafner added a comment - - edited I'm not aware of a workaround. That is the reason for the whole rework...
          Hide
          drulli Ulli Hafner added a comment -

          Released in 5.0.0-beta2.

          Show
          drulli Ulli Hafner added a comment - Released in 5.0.0-beta2.

            People

            Assignee:
            drulli Ulli Hafner
            Reporter:
            rs Reinhard S
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: