In our Jenkins Setup we are currently using the "internal shared library" (ssh://USERNAME@server:PORT/workflowLibs.git), which is implicit accessible via its "master" Branch.
Pipelines using that code are working fine.

Now, I´ve *cloned *that repo into a BitBucket Repo for "pretesting" changes with a demo project that resided in a "Folder" inside Jenkins.
I´ve configured this folder to use a "shared library" (the cloned one from the internal):

Name: cd_workflowlibs
Default version: master
Load implicitely: true
Allow default version to be overridden: true

The Url is like: ssh://git@licdci01.mycompany.net:7999/cd/workflowlibs.git
Branches to build: origin-bitbucket/master

When starting my pipeline, the library seems to be loaded correctly:

Loading library cd_workflowlibs@master
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin-bitbucket.url ssh://git@licdci01.mycompany.net:7999/cd/workflowlibs.git # timeout=10
Fetching upstream changes from ssh://git@licdci01.mycompany.net:7999/cd/workflowlibs.git
 > git --version # timeout=10
using GIT_SSH to set credentials SSH Bitbucket Access
 > git -c core.askpass=true fetch --tags --progress ssh://git@licdci01.mycompany.net:7999/cd/workflowlibs.git +refs/heads/*:refs/remotes/origin-bitbucket/*
 > git rev-parse refs/remotes/origin-bitbucket/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin-bitbucket/origin-bitbucket/master^{commit} # timeout=10
Checking out Revision 205f22f3563b2c5b224e41fdd8c53d1c22b041d2 (refs/remotes/origin-bitbucket/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 205f22f3563b2c5b224e41fdd8c53d1c22b041d2

The weird thing now is, that new scripts will be executed properly - but changes made to "old", existing scripts aren´t reflected.
It seems like the "old" scripts are still being used from the global, internal shared library location (where changes are not yet pushed).

After some tests, it came out that there´s an overlapping between scripts:
The old version is picked up from the internal repo,
the changed version is traced in the console.log - but not used.

It would be very helpfull to
a) be able to disable the internal repo at all
b) extend the output in console.log, which locations are used to find the *.groovy scripts.Currently the console contains only the locations of shared libraries - but no info about the internal repo which may also contains scripts.

Thanx for any improvements to make it more clear which script is choosen from which library/repo.

Torsten

See also https://groups.google.com/forum/#!searchin/jenkinsci-users/shared$20library%7Csort:relevance/jenkinsci-users/JTACzNkiqEU/nfcbR7fMCQAJ