[JIRA] (JENKINS-56323) The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

[juliehirani@hotmail.com (JIRA)]

Julie Shamji created an issue

Jenkins / JENKINS-56323 The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-28 12:13 Priority: Minor Reporter: Julie Shamji The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the previous/preceding build. This would allow a project to monitored for new and fixed issues from build to build for the same project. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner resolved as Fixed

This is already possible. You simply need to set ignoreQualityGate: true.

Jenkins / JENKINS-56323 The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed

Add Comment

[juliehirani@hotmail.com (JIRA)]

Julie Shamji commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build That means that I cannot use a quality gate to fail a build based on my thresholds against the previous build right?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

No, this is not correct: if you set ignoreQualityGate: true then always the previous build is used to compute new warnings. This has nothing to do with the quality gate itself. You still can fail a build based on the number of new warnings.

Add Comment

[juliehirani@hotmail.com (JIRA)]

Julie Shamji commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

Can the description of this option be updated to make this clear please? The current description does not suggest that the reference build is different when set to true.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

Do you have a suggestion? I'm not a native speaker and it is always somehow cumbersome to write such descriptions.

Add Comment

[juliehirani@hotmail.com (JIRA)]

Julie Shamji commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

I have set ignoreQualityGate to true and for the past two builds I am getting the same issues highlighted as new as the files have not been changed. Below are 3 examples of over 80 of these. The following may be important: The reference build shown against all these build is build #276 even though I have ignoreQualityGate true. Build #287 and a number of builds before this had projects failed to build but quality statistics were generated as I am using the -fn option. Should I be using the run always option instead? One of the changes in build #288 is a new version of checkstyle. Build #288 - I expected these failures as this project had failed to build so there were no statistics produced so these then look 'fixed'. ExportMsDocumentServiceImpl.java:130 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1 ExportMsDocumentServiceImpl.java:131 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1 ExportMsDocumentServiceImpl.java:132 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1 Build #289 - I did not expect this again. Which build was this evaluated against? The last build which failed or the last successful build? ExportMsDocumentServiceImpl.java:130 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1 ExportMsDocumentServiceImpl.java:131 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1 ExportMsDocumentServiceImpl.java:132 com.unisys.holmes2.h2ng.export.business.impl Indentation IndentationCheck Normal 1   On the description of the option, what about the following: 'If checked, then the result of the quality gate is ignored when selecting a reference build and will evaluate the issue age and new/existing against the previous build instead of the reference build. This option is disabled by default so a failing quality gate will be passed from build to build until the original reason for the failure has been resolved.'

Add Comment

[juliehirani@hotmail.com (JIRA)]

Julie Shamji commented on JENKINS-56323

Re: The new issues are 'new' compared to only one particular build for the project, the new issues section would be so much more useful if there was an option to compare against the last build

If the plugin compares against the last successful/unstable build, the following is more clear: 'If checked, then the result of the quality gate is ignored when selecting a reference build and will evaluate the issue age and new/existing against the last successful or unstable build instead of the reference build. This option is disabled by default so a failing quality gate will be passed from build to build until the original reason for the failure has been resolved.'

Add Comment