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

Cannot configure Global Pipeline Libraries

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Labels:
      None
    • Environment:
      Git plugin: 3.0
      Jenkins: 2.23
      Pipeline: Shared Groovy Libraries: 2.3
    • Similar Issues:

      Description

      With the release of 2.3, the jenkinsci/workflow-cps-global-lib-plugin offers a better way of managing global libraries.

      The current issue is that is does not seem possible to add repositories with either the Modern or the Legacy SCM options.

      Nothing pops up when selecting Modern.

      I can't select any credentials when trying to use Legacy mode even though we have some globally scoped.

        Attachments

          Issue Links

            Activity

            Hide
            suwantoc Suwanto Chandra added a comment -

            +1, with latest stack as of current :

            • core 2.23
            • git 3.0.0
            • workflow-cps-global-lib 2.3
            • workflow-aggregator 2.4
            Show
            suwantoc Suwanto Chandra added a comment - +1, with latest stack as of current : core 2.23 git 3.0.0 workflow-cps-global-lib 2.3 workflow-aggregator 2.4
            Hide
            zot24 Israel Sotomayor added a comment -

            Same problem here when loading the library from Jenkinsfile I can see:

            Loading library github.com/moltin/jenkins-pipeline-library@master
            Creating git repository in /var/jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6
             > git init /var/jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6 # timeout=10
            Setting origin to https://github.com/moltin/jenkins-pipeline-library.git
            

            But when trying to use the Global Configuration the following it's thrown:

            Loading library github.com/moltin/jenkins-pipeline-library@branches/master
            java.lang.NullPointerException
            	at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:74)
            	at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:150)
            	at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:131)
            

            So something different it's happening when loading the library from the Jenkinsfile vs Global configuration which works

            Show
            zot24 Israel Sotomayor added a comment - Same problem here when loading the library from Jenkinsfile I can see: Loading library github.com/moltin/jenkins-pipeline-library@master Creating git repository in / var /jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6 > git init / var /jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6 # timeout=10 Setting origin to https: //github.com/moltin/jenkins-pipeline-library.git But when trying to use the Global Configuration the following it's thrown: Loading library github.com/moltin/jenkins-pipeline-library@branches/master java.lang.NullPointerException at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:74) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:150) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:131) So something different it's happening when loading the library from the Jenkinsfile vs Global configuration which works
            Hide
            pianoroy Roy Tinker added a comment -

            Is there a workaround for this?

            Show
            pianoroy Roy Tinker added a comment - Is there a workaround for this?
            Hide
            jglick Jesse Glick added a comment -

            Regarding lack of options under Modern SCM, I am still waiting for SCM plugin maintainers to merge and release my PRs.

            Regarding lack of credentials under Legacy SCM, different PRs but the same story. I cannot force other maintainers to proceed.

            The NPE is a bug, which I have not heard of before; please file separately with details to reproduce from scratch.

            Show
            jglick Jesse Glick added a comment - Regarding lack of options under Modern SCM , I am still waiting for SCM plugin maintainers to merge and release my PRs. Regarding lack of credentials under Legacy SCM , different PRs but the same story. I cannot force other maintainers to proceed. The NPE is a bug, which I have not heard of before; please file separately with details to reproduce from scratch.
            Hide
            kwayman Kyle Wayman added a comment -

            We are seeing this behavior for Legacy SCM.

            Jesse Glick Has there been any update to your PRs?

            Show
            kwayman Kyle Wayman added a comment - We are seeing this behavior for Legacy SCM. Jesse Glick Has there been any update to your PRs?
            Hide
            mkobit Mike Kobit added a comment - - edited

            Kyle Wayman I think they were merged in, they are just waiting for the maintainer to release (see https://issues.jenkins-ci.org/browse/JENKINS-38048)

            Show
            mkobit Mike Kobit added a comment - - edited Kyle Wayman I think they were merged in, they are just waiting for the maintainer to release (see https://issues.jenkins-ci.org/browse/JENKINS-38048 )
            Hide
            jglick Jesse Glick added a comment -

            They were released.

            Show
            jglick Jesse Glick added a comment - They were released.

              People

              • Assignee:
                Unassigned
                Reporter:
                mkobit Mike Kobit
              • Votes:
                11 Vote for this issue
                Watchers:
                20 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: