{"thread":{"id":"62515","subject":"Inquiry on Onboarding a z/OS Machine to Git Community CI/CD Pipeline","startedAt":"2024-11-19T11:34:40Z","lastAt":"2024-11-19T22:30:06Z","messageCount":2,"participants":["Haritha D","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"507587","messageId":"898B3E90-1703-419D-A5FA-8BE9557744E5@ibm.com","threadId":"62515","inReplyTo":null,"subject":"Inquiry on Onboarding a z/OS Machine to Git Community CI/CD Pipeline","fromName":"Haritha D","fromEmail":"harithamma.d@ibm.com","sentAt":"2024-11-19T11:34:36Z","receivedAt":"2024-11-19T11:34:40Z","isPatch":false,"sender":{"key":"harithamma.d@ibm.com","avatar":"https://avatars.githubusercontent.com/u/112700353?v=4"},"body":"Hi Team,\n\nAs 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.\n\nCould 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.\n\nThank you for your assistance.\n\nBest regards,\nHaritha\n\n\n"},{"id":"507663","messageId":"Zz0Ra7PfJNhOcn7X@tapette.crustytoothpaste.net","threadId":"62515","inReplyTo":"898B3E90-1703-419D-A5FA-8BE9557744E5@ibm.com","subject":"Re: Inquiry on Onboarding a z/OS Machine to Git Community CI/CD Pipeline","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2024-11-19T22:30:03Z","receivedAt":"2024-11-19T22:30:06Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2024-11-19 at 11:34:36, Haritha D wrote:\n> Hi Team,\n> \n> 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.\n> \n> 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.\n\nMy recommendation is to set up a GitHub App that will be able to work\nwith the GitHub checks API and webhooks to kick off a job and report\nback on the status of your CI system.  Once that's set up, someone with\naccess to the git organization can add it to run CI jobs.\n\nIt might seem like a good idea to use a self-hosted GitHub Actions\nrunner on your platform, but (a) I don't think the runner runs on z/OS\nand (b) GitHub recommends against using self-hosted runners on public\nrepositories for security reasons[0].  For that reason, I don't think\nwe're going to enable that as an option, since it would be a\nvulnerability on our end (plus it would probably end poorly for you as\nwell, which we'd want to avoid).\n\nOne other alternatives is that if you can get things running in a\nvirtual machine well enough, that could be set up to run in emulation in\nGitHub Actions.  I've done this on my own personal repositories to set\nup Debian on arm64 as well as FreeBSD and NetBSD on amd64.\n\nOther folks may have other suggestions, so I'd definitely suggest seeing\nwhat they have to say.\n\nIn any event, before we set up CI, we'd probably want the tests to be\npassing. Is that the case now, or is more work required for that to\nhappen?\n\n[0] https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#self-hosted-runner-security\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"}]}