Hi, Github Enterprise provides callbacks/webhooks, which are executed on commit. So I have successfully tested the following:IMS Proclib members as files in a directory in a Github repository. Callback enabled that invokes a jenkins job, which in turn updates the IMS Proclib PDS.So you need Github Enterprise, Jenkins and ssh access to your z/OS, at best by using certificates. And anything additional you require beyond that.The jenkins job can be set up to do whatever you want in whatever language/method you want, it can be Ansible or just a bash script executed with ssh command on z/OS or ftp that submits a job using ftp spool api. There are all sorts of plugins for Jenkins.For example the jenkins job could update z/OS Parmlib and issue a z/OS command to refresh it afterwards. You could even add a step to the jenkins job to issue a display command and check the output if the refresh was successful, otherwise the jenkins job can be marked as failed.The jenkins job could call an IMS or CICS transaction or do some SQL to Db2 as part of the job. It could run an image copy or flash copy restore.The webhook/callback provides the names of the changed entities, so the update can be limited to just the member that has changed. After that is tested you can switch to github being the leading system and every commit to github will drive the change on z/OS. But for some tasks you might need a REXX or python scripts, bash scripts or even an assembler routine, because functionality to be called can sometimes be implemented easier running on z/OS.For review on github you could setup forks and each change is a pull request, which needs to be reviewed before merged/commited into the actual repo. The github web interfaces also allow for discussions, so there could be a thread with a discussion tied to a pull request or commit, which can be used for auditing. Of course its not limited to Jenkins, other solutions work as well, but just to give you the idea.
Hope it helps,Denis. -----Original Message----- From: kekronbekron <000002dee3fcae33-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Fri, Aug 6, 2021 4:51 pm Subject: Re: Rocket's Git and GitHub Enterprise So z/OS datasets are still the source of truth, and just a copy is being made into GitHub for visibility from the outside. I'm thinking of implementations that work the other way. Running Git server on Z**, hooking it to GitHub UI / web service, use GitHub Actions or other release mechanisms to rollout directly into live Z datasets. I mean live as in.. the way in which we normally do in Z. Just hooking GH into the usual current procedures/jobs/REXX in Z. **Noticed that Github Enterprise Server, the thing where you run the GitHub Enterprise servers yourself in 'your' cloud, or on-prem on VMware or OpenStack (lol) KVM... can't actually run in Z. That is, can it even run in Linux on Z, seeing that currently there's only OpenStack KVM flavour? Z can run KVM instead of z/OS but who's going to setup KVM just for this. - KB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 6th, 2021 at 7:04 PM, Pew, Curtis G <curtis....@austin.utexas.edu> wrote: > On Aug 5, 2021, at 11:32 PM, kekronbekron > 000002dee3fcae33-dmarc-requ...@listserv.ua.edu wrote: > > > > I periodically copy over the current libraries and push the changes to > > > GitHub. > > > > Do you mean push to GitHub and then 'build/deploy/copy over the current > > (PARMLIB) libraries using some build workflow? > > I have a script in my repository that runs commands like “rm sys1.parmlib/*; > cp "//'sys1.parmlib'" sys1.parmlib” (where “sys1.parmlib” is a directory in > the repository.) After running it I commit the changes and then push to > GitHub. > > > > It’s not perfect, but I can get some idea of when a change was made or > > > find an older version of a member that isn’t working right. > > > > > > Why is it not perfect, what would you want to work better? > > “Perfect” would be if git could manage the actual PDS(E)s, but that seems > like a lot to ask for. > > > ---------------------------------------------------------------------------------------------------- > > 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
