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.