-
New Feature
-
Resolution: Fixed
-
Minor
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?
- causes
-
JENKINS-64830 Add AGGREGATION_ONLY trend type to list values
-
- Resolved
-
- relates to
-
JENKINS-56178 Offer to select a specific build as the new reference in "reset" quality gate
-
- Open
-
- links to
[JENKINS-61196] Display one aggregation trend chart independently how often *Issues steps are used
Link | New: This issue relates to JENKINS-56178 [ JENKINS-56178 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Summary | Original: Define tool-specific quality gates | New: Display one aggregation trend chart independently how often *Issues step is used |
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 |
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. |
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 |
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?