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

Add an ability to specify external GIT repository for scripts

    XMLWordPrintable

    Details

    • Similar Issues:

      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.

        Attachments

          Activity

          Hide
          imod Dominik Bartholdi added a comment -

          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

          Show
          imod Dominik Bartholdi added a comment - 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
          Hide
          hakan Hakan Tandogan added a comment -

          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

          Show
          hakan Hakan Tandogan added a comment - 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
          Hide
          emangual Ed Mangual added a comment -

          That is correct.

          Show
          emangual Ed Mangual added a comment - That is correct.
          Hide
          imod Dominik Bartholdi added a comment -

          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

          Show
          imod Dominik Bartholdi added a comment - 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
          Hide
          emangual Ed Mangual added a comment -

          I have the same requirements as the users stated above. We would like for this plugin to have the ability to point to our own repo for groovy scripts.

          Show
          emangual Ed Mangual added a comment - I have the same requirements as the users stated above. We would like for this plugin to have the ability to point to our own repo for groovy scripts.
          Hide
          mjbros Mike Brosnan added a comment -

          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

          Show
          mjbros Mike Brosnan added a comment - 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
          Hide
          dserodio Daniel Serodio added a comment -

          This would be useful for us too. Because of company policy, all source code must be stored in our company's Git server.

          Show
          dserodio Daniel Serodio added a comment - This would be useful for us too. Because of company policy, all source code must be stored in our company's Git server.
          Hide
          domi Dominik Bartholdi added a comment -

          can't you just push to the scriptler repo?

          Show
          domi Dominik Bartholdi added a comment - can't you just push to the scriptler repo?

            People

            • Assignee:
              domi Dominik Bartholdi
              Reporter:
              joesephz Joe Zeldin
            • Votes:
              7 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated: