[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
Title: Message Title 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197907.155135602.1657.1564141140179%40Atlassian.JIRA.
[JIRA] (JENKINS-58679) An ability to see which module had reduced the coverage
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58679 An ability to see which module had reduced the coverage Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-07-26 11:36 Environment: Maven & Java 8 Labels: jenkins Priority: Minor Reporter: Julie Shamji We have a project with modules with many thousands of lines across all of them and the jenkins plugin aggregates the results from all of the result files and many changes could have been introduced across these modules. It would be good if the results could be drilled down to which module(s) had reduced coverage. This would help better identify which changes need to be updated with test coverage. If possible, this would be even better if the delete for each module, package and class could be drilled down with a delta.
[JIRA] (JENKINS-58678) On the build status page, show the result of the jacoco plugin
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58678 On the build status page, show the result of the jacoco plugin Issue Type: Improvement Assignee: Ognjen Bubalo Attachments: image-2019-07-26-12-29-26-633.png Components: jacoco-plugin Created: 2019-07-26 11:30 Environment: Maven & Java 8 Labels: jenkins Priority: Minor Reporter: Julie Shamji Currently in order to see why the build failed, the first step is to go the status page for a build. If any projects have failed to build, there are shown here. But when the build has failed for coverage reduction, I can only see this in the console output. It would be good if there were more details against the jacoco summary. These could include something like the warnings next generation plugin shown below where the quality gate is shown and the result. With this it would be good to see the same details as the console logs, e.g. which scope reduced and by how much.
[JIRA] (JENKINS-58677) An ability to mark the build as unstable rather than failed when the delta threshold is not met
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58677 An ability to mark the build as unstable rather than failed when the delta threshold is not met Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-07-26 11:26 Environment: Maven & Java 8 Labels: jenkins Priority: Minor Reporter: Julie Shamji There is an ability to mark a build as failed when the delta thresholds are not passed. Another option to mark as unstable instead will be useful as other plugins used may be dependent on the build status of the previous. E.g. warnings next generation will not use a previously failed build to use as a quality gate, but it can use an unstable build. Add Comment
[JIRA] (JENKINS-58676) An ability to compare against the previous build should be available
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58676 An ability to compare against the previous build should be available Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-07-26 11:23 Environment: Maven & Java 8 Labels: jenkins Priority: Minor Reporter: Julie Shamji Consider the following build sequence and results when delta thresholds are set: Build 1 - Line Coverage 15.5% Build 2 - Line Coverage 15.6% - Quality gate passed Build 3 - Line Coverage 15.5% - Quality gate failed and if configured, the build is marked as failed. Build 4 - Line Coverage 15.5% - Quality gate failed and if configured, the build is marked as failed. It would good to be able to choose that Build 4 does not fail as the coverage has not reduced from Build 3. This would make it easy to identify which builds have reduced coverage by the build status instead of having all builds failing until the coverage is increased.
[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
Title: Message Title 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
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Julie Shamji updated an issue Jenkins / JENKINS-58403 Issue marked as new when the issue did exist in a previous build but on a different line Change By: Julie Shamji Comment: This has been marked as a duplicate, Could you tell me which record this is a duplicate of so I can keep track of its progress please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200528.1562672143000.6549.1562753580142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Julie Shamji commented on JENKINS-58403 Re: Issue marked as new when the issue did exist in a previous build but on a different line This has been marked as a duplicate, Could you tell me which record this is a duplicate of so I can keep track of its progress please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200528.1562672143000.6547.1562753520124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Julie Shamji commented on JENKINS-58403 Re: Issue marked as new when the issue did exist in a previous build but on a different line I can confirm that there were no whitespace changes on this line. There were new lines added within 5 lines of this change. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200528.1562672143000.6513.1562752981222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58403 Issue marked as new when the issue did exist in a previous build but on a different line Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-09 11:35 Priority: Minor Reporter: Julie Shamji We have an issue which existed for a while, which is logged as which shows the issue is 24 days old: RequestAccessMergeProcessor.java:432 com.unisys.holmes2.h2ng.workflow.business.requestaccess Metrics JavaNCSSCheck Normal 24 In the next build, a change has been made to this file which moved this method to a new line, but the method remained unchanged. It is now logged as: RequestAccessMergeProcessor.java:434
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji commented on JENKINS-57857 Re: Dashboard - 'Select subset of tools' not working Hi Ulli, I have done some further testing. If I remove all the charts, then add a chart with no subset, I see the chart with the correct numbers. If I think add another chart with a different name with a subset, the first chart displayed with the subset counts instead of all counts and the other is blank when that one should display what the first is displaying. So the issue is when multiple charts are configured on the same dashboard with different settings, the last one is used for the first chart and all other charts are blank. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.23438.1559913900097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji commented on JENKINS-57857 Re: Dashboard - 'Select subset of tools' not working Please note that the chart without the subset set has counts which no not total correctly as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.22551.1559813580909%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji updated an issue Jenkins / JENKINS-57857 Dashboard - 'Select subset of tools' not working Change By: Julie Shamji Attachment: image-2019-06-06-10-32-45-851.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.22549.1559813580838%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji commented on JENKINS-57857 Re: Dashboard - 'Select subset of tools' not working Thanks Ulli, I did have aggregate on so last night I changed the configuration not to aggregate. This morning, I cannot see the previous aggregated results so added tool specific charts and these are still blank and the chart without a subset selected is not blank. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.22538.1559813040190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji updated an issue Jenkins / JENKINS-57857 Dashboard - 'Select subset of tools' not working Change By: Julie Shamji Attachment: image-2019-06-06-10-22-51-109.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.22535.1559812980885%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-57857 Dashboard - 'Select subset of tools' not working Issue Type: Improvement Assignee: Ulli Hafner Attachments: image-2019-06-05-10-52-27-057.png, image-2019-06-05-10-52-43-122.png, image-2019-06-05-10-53-17-304.png, image-2019-06-05-10-54-21-364.png, image-2019-06-05-10-54-29-062.png, image-2019-06-05-10-54-52-675.png Components: warnings-ng-plugin Created: 2019-06-05 09:54 Priority: Minor Reporter: Julie Shamji When wanting to display the statistics or chart with a subset of tools, the only option available is analysis and if I try to manually add the id of a tool, no statistics or chart is displayed. Add Comment
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Julie Shamji commented on JENKINS-56324 Re: Age does not look correct for new issues when compared with a reference build I have checked both builds outstanding XML and the id D0C733D61919401C83027E30C424C021 is not present in the files at all. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[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
Title: Message Title 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title
Julie Shamji commented on JENKINS-56324
Re: Age does not look correct for new issues when compared with a reference build
On the front end I see these issues first found in build #166:
DescriptionAndUrnQuickSearchTest.java:25
com.unisys.holmes2.h2ng.softentity.quickSearch.impl
Whitespace
WhitespaceAroundCheck
Normal
1
'=' is not followed by whitespace.
DescriptionAndUrnQuickSearchTest.java:33
com.unisys.holmes2.h2ng.softentity.quickSearch.impl
Whitespace
ParenPadCheck
Normal
1
'(' is followed by whitespace.
On build #183, as you can see its the same file and lines:
DescriptionAndUrnQuickSearchTest.java:25
com.unisys.holmes2.h2ng.softentity.quickSearch.impl
Whitespace
WhitespaceAroundCheck
Normal
1
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Julie Shamji commented on JENKINS-56324 Re: Age does not look correct for new issues when compared with a reference build They are new since the reference build and not fixed since the reference build. Literally every build since the reference build is showing every issue with age of 1, there are no issues with any other age. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[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
Title: Message Title 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-56324 Age does not look correct for new issues when compared with a reference build Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-28 12:26 Priority: Minor Reporter: Julie Shamji Our project is configured with a reference build, the console shows that build has been used for comparison, however the age for the issues are always shown as 1 even though they were flagged in a previous build. The console log for build #183 shows: 05:01:38 [Static Analysis] Using reference build ' #165' to compute new, fixed, and outstanding issues*05:01:38* [Static Analysis] Issues delta (vs. reference build): outstanding: 25055, new: 427, fixed: 517*05:01:38* [Static Analysis] Evaluating quality gates*05:01:38* [Static Analysis] -> WARNING - Total number of issues (Severity High): 291 - Quality Gate: 270*05:01:38* [Static Analysis] -> WARNING - Number of new issues: 427 - Quality Gate: 1*05:01:38* [Static Analysis] -> Some quality gates have been missed: overall result is WARNING*05:01:38* [Static Analysis] Health report is disabled - skipping*05:01:40* [Static Analysis] Created analysis result for 25482 issues (found 427 new issues, fixed 517 issues) Some of these issues have been introduced in build #166, but when I look at build #183, these same lines are shown with the Age of 1, shouldn't have an age relevant to the build it was first seen in?
[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
Title: Message Title 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
[JIRA] (JENKINS-55511) Using maven compiler and no issues are returned
Title: Message Title Julie Shamji commented on JENKINS-55511 Re: Using maven compiler and no issues are returned After using the sort option on the filename on the checkstyle issues list and going back to the Maven issues list I can now see the issues for Maven. When will the commit for this be released? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55513) 'No data available in table' can be improved to 'Loading' while the data is still being loaded
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-55513 'No data available in table' can be improved to 'Loading' while the data is still being loaded Issue Type: Improvement Assignee: Ulli Hafner Attachments: image-2019-01-10-12-28-04-008.png Components: warnings-ng-plugin Created: 2019-01-10 12:31 Priority: Minor Reporter: Julie Shamji While the dashboard issues list is loading, the 'No data available in table' message is displayed. This can be for some time when there are a large number of issues (We have over 2). This gives a false impression that there are no issues when there are. If a 'loading', message was displayed before it was evaluated there is no data, this would be clearer. Add Comment
[JIRA] (JENKINS-55511) Using maven compiler and no issues are returned
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-55511 Using maven compiler and no issues are returned Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-01-10-12-18-58-591.png Components: warnings-ng-plugin Created: 2019-01-10 12:22 Environment: Maven Compiler & Build Priority: Minor Reporter: Julie Shamji The analysis tool is finding issues using the Maven compiler, however they are not displayed on the issues list. I am aware that all issues are loaded and locally paged and sorted, however after 10 minutes, the issues list is not loaded. In addition to the issues not being loaded when we drill down to the Maven tool, the issues are also not loaded on the aggregate dashboard. This may be due to an issue loading the Maven issues. We are using the Checkstyle configuration as well and we can see the issues for those when we drill down to the Checkstyle tool.
