The git plugin includes configuration as code round trip tests like this one <https://github.com/jenkinsci/git-plugin/blob/master/src/test/java/jenkins/plugins/git/GlobalLibraryWithModernJCasCCompatibilityTest.java>. I like those tests because they confirm that configuration as code is well behaved with plugin use cases.
One of the round trip tests <https://ci.jenkins.io/job/Plugins/job/git-plugin/job/PR-1223/lastBuild/testReport/jenkins.plugins.git/GlobalLibraryWithModernJCasCCompatibilityTest/windows_8___Build__windows_8____roundTripTest/> fails on Windows with the upgrade from parent pom 4.34 to parent pom 4.35 <https://github.com/jenkinsci/git-plugin/pull/1223>. I've confirmed that the failure is consistent. I can see it on my Windows desktop computer and in the CI job <https://ci.jenkins.io/job/Plugins/job/git-plugin/job/PR-1223/lastBuild/testReport/jenkins.plugins.git/GlobalLibraryWithModernJCasCCompatibilityTest/windows_8___Build__windows_8____roundTripTest/> . The failure message reports java.lang.NoClassDefFoundError: jenkins/plugins/git/traits/package-info (wrong name: jenkins\plugins\git\traits\package-info) That looks suspiciously like a Windows specific issue with directory separators and might be a mistake attempting to call the constructor of the file "package-info". Any recommendations for a preferred solution? Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/19992613-b58c-4c8a-a368-5023f3bea6fan%40googlegroups.com.
