Well-known RFE, larger issue. There is a Remote Loader plugin but it does not cover quite the same functionality.

Here is how I manage to get this functionality, though we are using Stash instead of GitHub:

• Create workflow-libs repo in SCM
• Navigate to JENKINS_HOME/workflow-libs directory on jenkins server
• Do

  git clone YOUR_REPO_URL 

• • The key here is to make sure the repo is cloned right into the directory, not into a sub directory.
• Create a freestyle jenkins job and point it to your workflow-libs repo
• Add "Execute Shell" step to navigate to the JENKINS_HOME/workflow-libs directory and execute a git pull
  • e.g

     cd ../../workflow-libs
    git pull 

• If your GitHub repo uses web-hooks, configure it to notify jenkins when the repo has been committed to
• Configure the jenkins job to build when notified of a commit to the repo

Some of these steps may be a little different for GitHub as I am not familiar with the web-hook functionality there. I assume something similar could be achieved by a polling schedule from within the jenkins job.

This has worked well for us, especially in making UPDATES to global scripts. The one issue we have is that when committing a NEW script to the repo. After the push to the repo and the jenkins job has run to update the workflow-libs repo on the jenkins server, the new global script won't be available until after a jenkins restart. Before a restart you'll get a "Global Script Not Found" or similar error.

Hope this helps

mscharp I'm looking to do the same and find the https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Remote+Loader+Plugin somewhat lacking. Curious as why you have to restart? Does the original workflowLib.git have some commit hook that notifies Jenkins that the lib has been updated?