Thanks for reporting the problem. Can you provide more details on your system configuration? A support bundle would be ideal, since it provides lots of information in a single package that is easy to collect and easy to upload?
My reading of that exception in the JDK 7 javadoc shows
Thrown when an application tries to call an abstract method. Normally, this error is caught by the compiler; this error can only occur at run time if the definition of some class has incompatibly changed since the currently executing method was last compiled
. I think that must mean that I inadvertently changed a method signature of a method in a class that extends an Abstract class, or I changed an Abstract method definition.
I'm especially perplexed why I didn't see the problem in my testing before release, since I tested with JDK 8 + Jenkins 1.651.3 + Debian and I tested with JDK 7 + Jenkins 1.609.3 + Debian.
After installing the new version of the git plugin, did you restart your Jenkins instance?
There is a change/addition from wadahiro in AbstractGitSCMSource to add many more git options to the multi-branch plugin and the literate plugin (and anything else that uses the SCMSource interface). That change, and its successors 1, 2, 3, and the merge 4 (add tests, refine the code, etc.) worked well in my tests.
Are any of your pipeline plugins out of date?
Any other areas which you think might have relevant differences?