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

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

XMLWordPrintable

      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?

        1. image-2021-02-09-09-51-41-356.png
          image-2021-02-09-09-51-41-356.png
          22 kB

          [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 made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          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
          R. Fitzner made changes -
          Description Original: 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. 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.

           

          For example:

          For the {{publishIssues}} step you could add the option like this:
          {code:java}
          publishIssues trendChartType: 'AGGREGATION_ONLY'
          {code}
          This option would allow me using multipe {{publishIssues}} steps.

          Instead of {{this}}:
          {code:java}
          recordIssues aggregatingResults: true
          {code}
          you could align it with {{publishIssues}} and add the same options trendChartType

          What do you think?
          R. Fitzner made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Ulli Hafner made changes -
          Labels New: help-wanted user-experience
          Ulli Hafner made changes -
          Labels Original: help-wanted user-experience New: user-experience

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

              Created:
              Updated:
              Resolved: