What you can do is host a Git server instance e.g. on Linux for Z. This way you don't have to move your assets off the machine. If moving something off the platform is not the concern but rather who can access it then I'd suggest to restrict the repositories to the people that need to know. GitHub for Enterprise allows you to do exactly that. You can setup teams/organizations which have specific access to repositories and projects.
You'll have to answer the question on how you keep these assets in sync. In the end you would want to deploy your assets from Git to the actual Parmlib but I assume that this will be quite difficult to achieve. Cheers - David -----Ursprüngliche Nachricht----- Von: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Im Auftrag von Edgington, Jerry Gesendet: Donnerstag, 5. August 2021 16:48 An: IBM-MAIN@LISTSERV.UA.EDU Betreff: Re: Rocket's Git and GitHub Enterprise Rocket's port of Git, is not the server component, only the Git client. So, z/OS cannot act as the Git server. Jerry -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of kekronbekron Sent: Thursday, August 5, 2021 10:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rocket's Git and GitHub Enterprise This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. ________________________________________________________________________________________________________________________ Hmm.. what I mean is - I don't want GitHub Enterprise to have a copy of the repo. I understand GitHub E being 'the source' and then git clone etc. to local or z/OS. What I'm saying is... I want Rocket Git for z/OS to be 'the source', and then just use GitHub as the front-end for it. Don't want it to make copies of what's on Git for Z. Z should remain the system of record; don't want to put SYS1.PARMLIB for example on GitHub E. Even if GitHub E has auth etc., a very small percent of people in the company need to even be aware of SYS1.PARMLIB. Putting it on GitHub E means it's wide open for anyone in the company (with access to GitHub E). Just trying to understand what can be done to - a) keep Git on Z as 'the source' b) hide the MF-Git-linked repositories from the general GitHub E crowd - KB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, August 5th, 2021 at 7:17 PM, Pew, Curtis G <curtis....@austin.utexas.edu> wrote: > On Aug 5, 2021, at 8:27 AM, kekronbekron > 000002dee3fcae33-dmarc-requ...@listserv.ua.edu wrote: > > > If a company has GitHub Enterprise, can we hook that to Rocket's Git for > > z/OS, running on z/OS. > > > > Will that work without GitHub Enterprise making a copy/mirror of the > > original repos on Z? > > > > It would be amazing to keep Z's stuff managed by Git on Z, but then just > > use GitHub's excellent UI and workflows. > > Well, if the question is “can you use Rocket’s port of git for z/OS with > GitHub Enterprise?” then the answer is definitely yes. The University of > Texas has both, and I use them together all the time. > > I’m not sure what you’re asking with “GitHub Enterprise making a copy/mirror > of the original repos on z?” That’s not really the way git works: it’s a > distributed version control system, so you always have a local copy of the > repository. > > If I’m starting a new project, I usually create a repository on GitHub > Enterprise, and then clone it on whichever z/OS LPAR I’m working on, as well > as on my laptop. Then I use `git push` and `git pull` to keep them in sync. > > > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ------------------------------------ > > Pew, Curtis G > > curtis....@austin.utexas.edu > > > --------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
