[JIRA] (JENKINS-57480) All old warnings are reported as new after server migration

[mn@grp.de (JIRA)]

Marne created an issue

Jenkins / JENKINS-57480 All old warnings are reported as new after server migration Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-15 10:21 Environment: Jenkins ver. 2.164.3 warnings ng plugin ver. 5.0.0 Priority: Minor Reporter: Marne We migrated our Jenkins server to new hardware by installing a fresh new Jenkins on the new hardware and then coping the JENKINS_HOME directory from the old hardware to the new. Since then all warnings are reported as new. For example the report states: 7,643 new warnings 7,643 fixed warnings I was thinking that maybe the fingerprints of the builds from the old hardware and the fingerprints of the new hardware do not match. Any ideas how to investigate this issue further? I would prefer not to reset the quality gate to not miss a new warning introduced by a recent commit. Add Comment

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

[mn@grp.de (JIRA)]

Marne updated an issue

Jenkins / JENKINS-57480 All old warnings are reported as new after server migration

Change By: Marne We migrated our Jenkins server to new hardware by installing a fresh new Jenkins on the new hardware and then coping copying the JENKINS_HOME directory from the old hardware to the new. Since then all warnings are reported as new. For example the report states:

7,643 new warnings 7,643 fixed warnings I was thinking that maybe the fingerprints of the builds from the old hardware and the fingerprints of the new hardware do not match. Any ideas how to investigate this issue further? I would prefer not to reset the quality gate to not miss a new warning introduced by a recent commit.

Add Comment

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

Ulli Hafner commented on JENKINS-57480

Re: All old warnings are reported as new after server migration The file path is part of the fingerprint (and equals). Are you running the builds on the master?

Add Comment

[mn@grp.de (JIRA)]

Marne commented on JENKINS-57480

Re: All old warnings are reported as new after server migration

Thanks for your quick response. The file paths should be identical. We only migrated the master. The slaves performing the build are still using the same hardware as before.

Add Comment

[mn@grp.de (JIRA)]

Marne updated an issue

Jenkins / JENKINS-57480

All old warnings are reported as new after server migration

Change By: Marne We migrated our Jenkins server (master) to new hardware by installing a fresh new Jenkins on the new hardware and then copying the JENKINS_HOME directory from the old hardware to the new. All slaves performing the actual builds were not touched. Since then all warnings are reported as new. For example the report states:

7,643 new warnings 7,643 fixed warnings I was thinking that maybe the fingerprints of the builds from the old hardware and the fingerprints of the new hardware do not match. Any ideas how to investigate this issue further? I would prefer not to reset the quality gate to not miss a new warning introduced by a recent commit.

Add Comment

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

Ulli Hafner commented on JENKINS-57480

Re: All old warnings are reported as new after server migration You can check the xml files in the build folder of the build on the new and the old build (*-issues.xml). Maybe a simple diff shows the changed property between the builds. (Or select an issue in both build xml files and compare the properties).

Add Comment

[mn@grp.de (JIRA)]

Marne commented on JENKINS-57480

Re: All old warnings are reported as new after server migration

Thanks, with this hint I found which configuration mistake of ours caused the problem. The fingerprints of the newer builds all started with "FALLBACK". So Jenkins was not able to read the files. It turned out that we did not configure the source file encoding. Not sure if the encoding Jenkins tried to read the files with changed due to the migration or what caused this to suddenly become a problem but after specifying the correct encoding the issue delta is correct again. Thank you very much for your help!

Add Comment

[mn@grp.de (JIRA)]

Marne closed an issue as Not A Defect

Configuration problem

Jenkins / JENKINS-57480

All old warnings are reported as new after server migration

Change By: Marne Status: Open Closed Resolution: Not A Defect

Add Comment

[mn@grp.de (JIRA)]

Marne updated an issue

Jenkins / JENKINS-57480 All old warnings are reported as new after server migration

Change By: Marne Comment: Configuration problem

Add Comment