Also waiting on this issue to be resolved. While using the 'Legacy SCM' option works for us, it in turn exposes us to JENKINS-44075 meaning that we can not specify the shared library version to check out in our Jenkinsfile.
Also waiting on this issue to be resolved. The 'Legacy SCM' doesn't work for us, because it doesn't able us to use 'system' scoped credentials. The goal for us is to able people using exposed shared library without having the access to the repository itself.
Reproduced. The attached JENKINS-43802.diff solves the issue in the reported case and so confirms my hypothesis of 2017-08-21, but it is not thread-safe, and will not work for non-multibranch projects. The thread safety could be addressed with some hacks, but the extension to plain projects seems possible only with some API changes and their use in various SCM plugins.
Mark Waite is there a reason you just marked this issue (and another one similar to it) FIXED BUT UNRELEASED when there is in fact a release with the fix?