On 2024-11-19 at 11:34:36, Haritha D wrote: > Hi Team, > > As we are working on enabling Git on the z/OS platform, and we believe integrating a z/OS machine into the Git community's CI/CD pipeline could be valuable for testing and validation. > > Could you please provide guidance on how to proceed with onboarding a z/OS system as part of the community's CI/CD pipeline? We would appreciate any information on the technical requirements and necessary steps for this integration. My recommendation is to set up a GitHub App that will be able to work with the GitHub checks API and webhooks to kick off a job and report back on the status of your CI system. Once that's set up, someone with access to the git organization can add it to run CI jobs. It might seem like a good idea to use a self-hosted GitHub Actions runner on your platform, but (a) I don't think the runner runs on z/OS and (b) GitHub recommends against using self-hosted runners on public repositories for security reasons[0]. For that reason, I don't think we're going to enable that as an option, since it would be a vulnerability on our end (plus it would probably end poorly for you as well, which we'd want to avoid). One other alternatives is that if you can get things running in a virtual machine well enough, that could be set up to run in emulation in GitHub Actions. I've done this on my own personal repositories to set up Debian on arm64 as well as FreeBSD and NetBSD on amd64. Other folks may have other suggestions, so I'd definitely suggest seeing what they have to say. In any event, before we set up CI, we'd probably want the tests to be passing. Is that the case now, or is more work required for that to happen? [0] https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#self-hosted-runner-security -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
