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

Add aggregation and subview for multi-configuration projects

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-plugin
    • None

      Issue added as a result of discussion from https://issues.jenkins-ci.org/browse/JENKINS-6772.

      In multi-configuration projects it would be preferable to have the warnings plugin show a different view for each matrix element. On the main page for the multi-configuration project we could have a aggregated view, showing the number of warnings for each matrix element.

      One specific case would be when having different compiler versions on one axis, and operating systems on the other. It would then be interesting to see warnings for the compiler gcc 4.4.2 compiling the project on RHEL4, as well as the warnings for gcc 4.6.1 compiling the project on RHEL5. The aggregated view would then show number of warnings for gcc 4.4.2/RHEL4 and gcc 4.6.1/RHEL5 on the main page, and the subviews would show the actual warnings for each combination of gcc and OS on the subpage.

      Let me know if I need to clarify further.

          [JENKINS-11225] Add aggregation and subview for multi-configuration projects

          Roland Schulz added a comment -

          The view I would be most interested in, is the Warnings Tab under Details on the WarningsResults page for all axis with >0 warnings under each other on one page. Similar to the lower part ("Failed tests") of the testResults page. The 2nd most interesting view to me would be a table with the axis (configuration names) as rows and the warning types as columns. And the content of the table would show the total number of warnings for that type and configuration. One could also show the number of high,normal,low priority warnings in parenthesis as content.

          Roland Schulz added a comment - The view I would be most interested in, is the Warnings Tab under Details on the WarningsResults page for all axis with >0 warnings under each other on one page. Similar to the lower part ("Failed tests") of the testResults page. The 2nd most interesting view to me would be a table with the axis (configuration names) as rows and the warning types as columns. And the content of the table would show the total number of warnings for that type and configuration. One could also show the number of high,normal,low priority warnings in parenthesis as content.

          I'm starting using this plugin. I use a matrix project for building applications for a gcc4 host (Ubuntu) and an embedded gcc4 for ARM on one axis. Second axis is for debug and release. All 4 combinations generate different number of warnings.
          So from my point of view it would be nice to accumulate the sums, like the xUnit plugin does. The source files have different pathes because of individual subdirectories in the workspace, right?
          Would be great to have this update, this plugin is awesome anyway!

          Andreas Zoufal added a comment - I'm starting using this plugin. I use a matrix project for building applications for a gcc4 host (Ubuntu) and an embedded gcc4 for ARM on one axis. Second axis is for debug and release. All 4 combinations generate different number of warnings. So from my point of view it would be nice to accumulate the sums, like the xUnit plugin does. The source files have different pathes because of individual subdirectories in the workspace, right? Would be great to have this update, this plugin is awesome anyway!

          Wael Darwich added a comment -

          This looks an old issue that has been waiting for long, I suggest a quick fix would be to show no warnings at all on the job root, and only show warnings at configuration level, at least this is more correct than showing the first configuration if configurations differ

          I use multi configurations for Win/Linux/Mac builds, and different compilers generate different warnings, a better solution would be to show all configurations warnings on the job root, either on separate diagrams as a quick way, or even better to give the user the option to sum warnings from different configurations on the same diagram

          Anyway thanks for everybody helping to make Jenkins a better system, different use cases using different plugins get endless issues to sort, unfortunately the more you do the more you find yourself need to do

          Wael Darwich added a comment - This looks an old issue that has been waiting for long, I suggest a quick fix would be to show no warnings at all on the job root, and only show warnings at configuration level, at least this is more correct than showing the first configuration if configurations differ I use multi configurations for Win/Linux/Mac builds, and different compilers generate different warnings, a better solution would be to show all configurations warnings on the job root, either on separate diagrams as a quick way, or even better to give the user the option to sum warnings from different configurations on the same diagram Anyway thanks for everybody helping to make Jenkins a better system, different use cases using different plugins get endless issues to sort, unfortunately the more you do the more you find yourself need to do

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/test/java/plugins/WarningsPluginTest.java
          src/test/resources/warnings_plugin/matrix-warnings.txt
          http://jenkins-ci.org/commit/acceptance-test-harness/704943e6230379f414987621c4abc4d5eeb988e1
          Log:
          JENKINS-11225 Added a test case that verifies the current behavior.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/WarningsPluginTest.java src/test/resources/warnings_plugin/matrix-warnings.txt http://jenkins-ci.org/commit/acceptance-test-harness/704943e6230379f414987621c4abc4d5eeb988e1 Log: JENKINS-11225 Added a test case that verifies the current behavior.

          Ulli Hafner added a comment -

          I'm not sure if there is still something to do in this issue? I added a test case (https://github.com/jenkinsci/acceptance-test-harness/commit/704943e6230379f414987621c4abc4d5eeb988e1) that builds with an axis of three configurations. For each configuration the correct number of warnings is reported and visualized. Even more, on the root action, the sum of the three actions is shown. I don't use matrix projects on my own so I might not get the point here: is this not the expected behavior?

          Ulli Hafner added a comment - I'm not sure if there is still something to do in this issue? I added a test case ( https://github.com/jenkinsci/acceptance-test-harness/commit/704943e6230379f414987621c4abc4d5eeb988e1 ) that builds with an axis of three configurations. For each configuration the correct number of warnings is reported and visualized. Even more, on the root action, the sum of the three actions is shown. I don't use matrix projects on my own so I might not get the point here: is this not the expected behavior?

          Roland Schulz added a comment -

          What would be nice is the root would show which configuration has which warning. Multiple options of how to show that information:

          • show the configuration name as extra information (for "Folder", "Files" and "Warnings" tabs it could be its own column. For details it should be added to the header)
          • add a new tab "Configuration". It works like "Details" but the warnings are grouped by configurations
          • have the whole table with the tabs shown once per configuration

          The reason one of those options would be useful is that we have a large number of configurations in our matrix job (>30) and it is useful to quickly which configurations have the same set of warnings and whether additional warnings are only present for individual configurations.

          Roland Schulz added a comment - What would be nice is the root would show which configuration has which warning. Multiple options of how to show that information: show the configuration name as extra information (for "Folder", "Files" and "Warnings" tabs it could be its own column. For details it should be added to the header) add a new tab "Configuration". It works like "Details" but the warnings are grouped by configurations have the whole table with the tabs shown once per configuration The reason one of those options would be useful is that we have a large number of configurations in our matrix job (>30) and it is useful to quickly which configurations have the same set of warnings and whether additional warnings are only present for individual configurations.

          Ulli Hafner added a comment -

          Ok, I understand. There is nothing missing in the graphs or in the overview, the details on the root need to be enhanced.

          If you don't mind: could you please file individual issues for these feature request. I'm almost sure that this requires some time so tracking them individually would be easier. Please also consider setting the priorities so we can better see where to start first.

          Ulli Hafner added a comment - Ok, I understand. There is nothing missing in the graphs or in the overview, the details on the root need to be enhanced. If you don't mind: could you please file individual issues for these feature request. I'm almost sure that this requires some time so tracking them individually would be easier. Please also consider setting the priorities so we can better see where to start first.

          Roland Schulz added a comment -

          I meant those 3 options as alternatives (of which the easiest to do would suffice) not as 3 independent things. Thus I only created one issue: 26913.

          Roland Schulz added a comment - I meant those 3 options as alternatives (of which the easiest to do would suffice) not as 3 independent things. Thus I only created one issue: 26913.

          Ulli Hafner added a comment - - edited

          Closing this issue since the initial request is fixed. Two additional issues are still open:

          • JENKINS-26913: add the configuration names to the warnings and visualize these properties in the detail view
          • JENKINS-25905: add additional configuration options to the aggregated graph that (one graph per configuration).

          Please use one of these issues for comments.

          Ulli Hafner added a comment - - edited Closing this issue since the initial request is fixed. Two additional issues are still open: JENKINS-26913 : add the configuration names to the warnings and visualize these properties in the detail view JENKINS-25905 : add additional configuration options to the aggregated graph that (one graph per configuration). Please use one of these issues for comments.

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          analysis-test
          checkstyle
          pmd
          warnings
          http://jenkins-ci.org/commit/analysis-suite-plugin/79aa9ccd51f0fdf7f095e8a9aa5148d17af88a39
          Log:
          JENKINS-11225 Added a test case that verifies the current behavior.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: analysis-test checkstyle pmd warnings http://jenkins-ci.org/commit/analysis-suite-plugin/79aa9ccd51f0fdf7f095e8a9aa5148d17af88a39 Log: JENKINS-11225 Added a test case that verifies the current behavior.

            drulli Ulli Hafner
            jeinor Jonas Oscarsson
            Votes:
            7 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: