[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build

[juliehir...@hotmail.com (JIRA)]

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 'XXXX #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? 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.