Add an ability to specify external GIT repository for scripts

Details

Description

It would be sensible to add an ability to specify an external scripts GIT repo, not only GitHub one.
We have a big collection of scripts, could not be shared either to everybody from open space or from organization. We have our own Gerrit, where these scripts are stored. It would be a great feature for us to be able to specify this repo as a source of scripts.

If this plugin allowed access to use a different external repo, I believe that enterprise users of Jenkins would still contribute some scripts to github and scriptler, but the main body of scripts would be from an internal repo.

If scriptler is not updated to allow an internal catalog, then teams will just fork the code to build their own internal versions of the plugin

Mike Brosnan
added a comment - 2014-12-01 13:41 If this plugin allowed access to use a different external repo, I believe that enterprise users of Jenkins would still contribute some scripts to github and scriptler, but the main body of scripts would be from an internal repo.
If scriptler is not updated to allow an internal catalog, then teams will just fork the code to build their own internal versions of the plugin

Dominik Bartholdi
added a comment - 2017-01-06 16:19 just to be clear, you would like to have an inhouse catalog (1) - a list of scripts that can be imported into individual jenkins instances via scriptler?
(1) https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-Catalogs

Hakan Tandogan
added a comment - 2017-01-08 20:04 Dominik Bartholdi , can I launch this "Import" step through a groovy script as well?
That way, I could have a job that listens to my in-house git repository, and imports all new/changed scripts on every push. Which would be as good as specifiying an external GIT repo.
Of course, if I manage the scripts externally, a way to forbid direct changes through the Jenkins UI would be necessary, but this is the next step

Dominik Bartholdi
added a comment - 2017-01-09 07:33 Hakan Tandogan no sorry, that's not possible - but there is an extension point you can implement to add a new catalog: org.jenkinsci.plugins.scriptler.share.ScriptInfoCatalog