Your assumption is correct, see this issue:
https://issues.jenkins-ci.org/browse/JENKINS-38424?focusedCommentId=271289&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-271289
This is also related: https://issues.jenkins-ci.org/browse/JENKINS-38550
("Pipeline Libraries
I am making an assumption that "Modern SCM" is some new Jenkins SCM API not
yet supported by most common SCMs - so I am just ignoring it and using
Legacv SCM
As for ${library.name.version} - you use it if you specify branch/tag in
GIT or in URL for SVN
Basically when you load the library with
Hellojust giving this thread a bump as I'm having the same questions.
What exactly is supposed to be the configuration for Modern SCM? I have
been able to get it to work using the Legacy SCM to point at my git repo.
On Monday, September 12, 2016 at 3:48:02 AM UTC-4, Sverre Moe wrote:
>
> T
There has been changes in the Global Pipeline Library plugin
https://issues.jenkins-ci.org/browse/JENKINS-31155
Jenkins Configuration => Global Pipeline Libraries
Choosing "Modern SCM" the next drop down list is empty. What does this
option actually do?
Choosing "Legacy SCM" I'm able to define a
