Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38550

"Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist

XMLWordPrintable

      I already griped at danielbeck, but figured I would file a proper ticket

      Right now there are no released versions of "Modern SCM" that would fill in the drop-down in the "Pipeline Libraries 'Add'" section. The fact that this is shown, and is the default source for Pipeline Libraries is confusing.

      The ideal fix, IMO, would be to only show "Modern SCM" if t here are implementations loaded into the Jenkins instance which support those extension points.

        1. modern-scm-lol.png
          modern-scm-lol.png
          28 kB

          [JENKINS-38550] "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist

          Gigi Lentini added a comment -

          Hi,
          I was playing with the configuration, and noticed the same problem.
          According to the documentation, the Git plugin should be supported.

          I've downloaded all the needed dependencies, but still no implementation is displayed.
          Do you know which are the implementation properly supported?

          Gigi Lentini added a comment - Hi, I was playing with the configuration, and noticed the same problem. According to the documentation, the Git plugin should be supported. I've downloaded all the needed dependencies, but still no implementation is displayed. Do you know which are the implementation properly supported?

          Christopher Orr added a comment -

          lentini: The users' mailing list or the IRC channel, rather than JIRA, are the places to get help.

          But if you have the Git plugin installed, then when you choose "Legacy SCM" instead of "Modern SCM" in the drop-down, you'll see "Git" as an option.

          At some point in the near-ish future, the Git plugin will support the API required to show up as a "Modern SCM" in the drop-down.

          Christopher Orr added a comment - lentini : The users' mailing list or the IRC channel, rather than JIRA, are the places to get help. But if you have the Git plugin installed, then when you choose "Legacy SCM" instead of "Modern SCM" in the drop-down, you'll see "Git" as an option. At some point in the near-ish future, the Git plugin will support the API required to show up as a "Modern SCM" in the drop-down.

          Gigi Lentini added a comment - - edited

          orrc thanks for the tips, I'll post to the mailing list next time. But since I've seen the ticket opened with the same problem I had, it was quicker for me to reply here

          I did as you said indeed, I'll wait for the Git plugin proper support.
          Still I think the documentation suggests Git and Subversion plugin already have that support, but it's not the case.

          Gigi Lentini added a comment - - edited orrc thanks for the tips, I'll post to the mailing list next time. But since I've seen the ticket opened with the same problem I had, it was quicker for me to reply here I did as you said indeed, I'll wait for the Git plugin proper support. Still I think the documentation suggests Git and Subversion plugin already have that support, but it's not the case.

          Jesse Glick added a comment -

          “Already” meaning “if you build from my pull requests”, alas.

          Jesse Glick added a comment - “Already” meaning “if you build from my pull requests”, alas.

          Jesse Glick added a comment -

          I already updated the docs BTW.

          Jesse Glick added a comment - I already updated the docs BTW.

            jglick Jesse Glick
            rtyler R. Tyler Croy
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: