[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 Ulli Hafner commented on JENKINS-58403 Re: Issue marked as new when the issue did exist in a previous build but on a different line I think I need to find some time to port https://github.com/jenkinsci/analysis-core-plugin/pull/49 to the new API. 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.6545.1562753400158%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 Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-58403 Issue marked as new when the issue did exist in a previous build but on a different line Change By: Ulli Hafner Status: Open Closed Resolution: Duplicate 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.6543.1562753341281%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 Ulli Hafner commented on JENKINS-58403 Re: Issue marked as new when the issue did exist in a previous build but on a different line The comparison is using a two pass algorithm: in the first pass the properties of the warning are compared. If one property differs (e.g., line number) then this warning is moved to a second pass. In the second pass, the actual code is compared. This is currently done by checking the context above and below the warning (5 lines). Did the content (or whitespace) in the surrounding lines 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.5906.1562703480199%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
