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

Display one aggregation trend chart independently how often *Issues steps are used

      Please make the steps recordIssues and publishIssues configurable in the way that Jenkins will display one aggregation trend chart and no scanner-specific trend chart on the Jenkins job status page independent how often the steps are configured/called.

       

      For example:

      For the publishIssues step you could add the option like this:

      publishIssues trendChartType: 'AGGREGATION_ONLY'
      

      This option would allow me using multipe publishIssues steps.

      Instead of this:

      recordIssues aggregatingResults: true
      

      you could align it with publishIssues and add the same options trendChartType

      What do you think?

          [JENKINS-61196] Display one aggregation trend chart independently how often *Issues steps are used

          R. Fitzner created issue -
          R. Fitzner made changes -
          Link New: This issue relates to JENKINS-56178 [ JENKINS-56178 ]

          Ulli Hafner added a comment -

          You can already specify different quality gates for different tools. Just use one recordIssues step for each tool. Or what exactly are you trying to achieve?

          Ulli Hafner added a comment - You can already specify different quality gates for different tools. Just use one recordIssues step for each tool. Or what exactly are you trying to achieve?
          Ulli Hafner made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          R. Fitzner added a comment - - edited

          I have configured my pipeline in the way that it uses scanForIssues step for each tool independently (e.g. java(), javaDoc(), taskScanner()).

          At the end there is a pipeline stage which always posts the results (depending on the results of the previously Gradle task and if a scan has been done) like this:

          publishIssues issues: [java, javaDoc, ...]
          

          Here I can configure qualityGates which will affect all tools.

          I could configure recordIssues or scanForIssues plus publishIssues for each tool scan, but then on the main status page of a Jenkins job, Jenkins shows multiple trend charts for each tool separately.
          For the publishIssues step there is no option like this:

          publishIssues trendChartType: 'AGGREGATION_ONLY'
          

          This option would allow me using multipe publishIssues steps.

          Only for recordIssues I can do that:

          recordIssues aggregatingResults: true
          

          But using recordIssues I cannot suppress showing all other trend charts of each tool scan.

          In the end this is the only option I have found that the status page shows the aggregation trend chart only!

          I also noticed this has a bad side effect when it comes to dashbords. Using this solution ends up in the fact that I can display only the aggregated values, not separated by tools.

          R. Fitzner added a comment - - edited I have configured my pipeline in the way that it uses scanForIssues step for each tool independently (e.g. java(), javaDoc(), taskScanner()). At the end there is a pipeline stage which always posts the results (depending on the results of the previously Gradle task and if a scan has been done) like this: publishIssues issues: [java, javaDoc, ...] Here I can configure qualityGates which will affect all tools . I could configure recordIssues  or scanForIssues plus publishIssues for each tool scan, but then on the main status page of a Jenkins job, Jenkins shows multiple trend charts for each tool separately . For the publishIssues step there is no option like this: publishIssues trendChartType: 'AGGREGATION_ONLY' This option would allow me using multipe publishIssues steps. Only for recordIssues I can do that: recordIssues aggregatingResults: true But using recordIssues I cannot suppress showing all other trend charts of each tool scan. In the end this is the only option I have found that the status page shows the aggregation trend chart only! I also noticed this has a bad side effect when it comes to dashbords. Using this solution ends up in the fact that I can display only the aggregated values, not separated by tools.

          Ulli Hafner added a comment - - edited

          I see. Then please rework the issue description and title so it is clear what actually should be done. Adding the trendChartType property to publishIssues should not be hard...

          Ulli Hafner added a comment - - edited I see. Then please rework the issue description and title so it is clear what actually should be done. Adding the trendChartType property to publishIssues should not be hard...
          R. Fitzner made changes -
          Summary Original: Define tool-specific quality gates New: Display one aggregation trend chart independently how often *Issues step is used
          R. Fitzner made changes -
          Description Original: As soon as the pipeline measures more issues because a new tool is detected used by the git repository then it is quite possible that the defined quality gate will always fail. This is a gap in the plugin. It is not possible to define tool-specific quality gates. New: Please make
          R. Fitzner made changes -
          Description Original: Please make New: Please make the steps {{recordIssues}} and {{publishIssues}} configurable in the way that Jenkins will display one aggregation trend chart and no scanner-specific trend chart on the Jenkins job status page independent how often the steps are configured/called.
          R. Fitzner made changes -
          Summary Original: Display one aggregation trend chart independently how often *Issues step is used New: Display one aggregation trend chart independently how often *Issues steps are used

            drulli Ulli Hafner
            rf R. Fitzner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: