Couldn't you use a "git clone" (or git clone --mirror) to copy them to a
separate repo, then config a remote that would allow you to "git push" them
to your corporate location?  That will retain the history of the repo and
the structure (if it matters to you).

Mark Waite

On Mon, Feb 27, 2017 at 3:31 PM Owen B. Mehegan <o...@nerdnetworks.org>
wrote:

> I've been using Pipeline global libraries since their inception, storing
> them in the built-in Git server within Jenkins. It's about time that I
> moved them into my company's regular Git repo, where others can collaborate
> on them more easily. What's the right way to do this? Seems like I should
> copy the libraries to the new external repo, then 'git rm' them from the
> existing internal repo, and then configure Jenkins appropriately to pull
> from the external SCM. Am I missing anything else?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/07d28411-2272-424a-9ab8-e312799274e5%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/07d28411-2272-424a-9ab8-e312799274e5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEDC_hvG_JposW0zrHXg4QvgQTynCnD8zpgAysvzs19%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to