[JIRA] (JENKINS-61196) Define tool-specific quality gates

13 views
Skip to first unread message

fitzner@ifao.net (JIRA)

unread,
Feb 24, 2020, 5:20:02 AM2/24/20
to jenkinsc...@googlegroups.com
R. F. created an issue
 
Jenkins / New Feature JENKINS-61196
Define tool-specific quality gates
Issue Type: New Feature New Feature
Assignee: Ulli Hafner
Components: warnings-ng-plugin
Created: 2020-02-24 10:19
Priority: Minor Minor
Reporter: R. F.

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.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ullrich.hafner@gmail.com (JIRA)

unread,
Feb 24, 2020, 6:23:03 AM2/24/20
to jenkinsc...@googlegroups.com
Ulli Hafner commented on New Feature JENKINS-61196
 
Re: Define tool-specific quality gates

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?

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 4, 2020, 4:26:03 PM3/4/20
to jenkinsc...@googlegroups.com
Ulli Hafner resolved as Not A Defect
Change By: Ulli Hafner
Status: Open Resolved
Resolution: Not A Defect
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

fitzner@ifao.net (JIRA)

unread,
Mar 5, 2020, 4:45:02 AM3/5/20
to jenkinsc...@googlegroups.com
R. F. commented on New Feature JENKINS-61196

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 notice 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.

fitzner@ifao.net (JIRA)

unread,
Mar 5, 2020, 4:48:02 AM3/5/20
to jenkinsc...@googlegroups.com
R. F. edited a comment on New Feature JENKINS-61196
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:
{code:java}

publishIssues issues: [java, javaDoc, ...]
{code}
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:
{code:java}
publishIssues trendChartType: 'AGGREGATION_ONLY'
{code}

This option would allow me using multipe {{publishIssues}} steps.

Only for {{recordIssues}} I can do that:
{code:java}
recordIssues aggregatingResults: true
{code}

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 notice 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.

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 5, 2020, 5:02:03 AM3/5/20
to jenkinsc...@googlegroups.com

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...

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 5, 2020, 5:03:03 AM3/5/20
to jenkinsc...@googlegroups.com
Ulli Hafner edited a comment on New Feature JENKINS-61196
Reply all
Reply to author
Forward
0 new messages