Hello....just 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: > > 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 git repository for the library. > > > <https://lh3.googleusercontent.com/-K6GYJCRmDJY/V9ZdcNW8A3I/AAAAAAAAEnw/eKdj8AMEaT4P2h29hAriZ1NZUMw82Yv8gCLcB/s1600/pipelinelibrary1.png> > > > <https://lh3.googleusercontent.com/-VSRoWmaCjn4/V9ZdlZNHzNI/AAAAAAAAEn4/nh1BoH4WwZk8jRL26nKqZrxwVtFxe24QwCLcB/s1600/pipelinelibrary2.png> > > > > > According to the documentation: > >> It can be used in two modes: a legacy mode in which there is a single Git >> repository hosted by Jenkins itself, to which you may push changes; and a >> more general mode in which you may define libraries hosted by any SCM in a >> location of your choice. > > > Should it not be the other way around for the modes in configuration? > Modern SCM should have option to add SCM. > > > > The best way to specify the SCM is using an SCM plugin which has been >> specifically updated to support a new API for checking out an arbitrary >> named version (Modern SCM option). Initially the Git and Subversion plugins >> have this modification > > Choosing Modern SCM there is no option in the drop down list. Neither git > nor subversion. Though they are with Legacy SCM. > > > > If your SCM plugin has not been integrated, you may select Legacy SCM and >> pick anything offered. In this case, you need to include >> ${library.yourLibName.version} somewhere in the configuration of the SCM, >> so that during checkout the plugin will expand this variable to select the >> desired version. > > For a library in a git repository would I need to tag a specific version? > > > --- > > > It is great that we now can use a shared library stored with our own Git > remote repository server. However until we transition to that have > workflowLibs.git work as before. > > > If I move the shared library to a different SCM I would probably need to > remove workflowLibs.git otherwise how would Jenkins know which one to load > as I need to load it implicitly. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/0b43e653-335d-4f82-94d2-366c9fb6a214%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
