MacOS Shared Runner Machine Manifests
I'm creating this issue to capture the discussion started in https://gitlab.slack.com/archives/CMB49D9FZ/p1658185255845189.
The idea behind this feature is to create a place to provide information to users to help them more easily debug issues with their CI jobs on MacOS Shared Runners. CircleCI provides similar information, for example:
https://circleci.com/docs/testing-ios#supported-xcode-versions https://circle-macos-docs.s3.amazonaws.com/image-manifest/v6269/index.html
@akohlbecker mentioned that some of this information is available in the toolchain.yml files https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/macstadium/orka/-/blob/main/toolchain/monterey.yml, but not all of it.
I attempted to create a simple inspection script to get this information by running a CI job https://gitlab.com/gitlab-org/incubation-engineering/devops-for-mobile-apps/macos-runner-inspector/-/pipelines/594633300/builds
Assuming this information is something we want to publish (up for debate), there are a couple of ways I could see approaching it:
- Create a CI job that auto generates the manifests and publishes them to some location, perhaps a micro GitLab pages site. This job could run on a schedule and keep the manifests up to date in realtime.
- Manually write and publish the manifests to the docs, and create a CI job that runs on a schedule to verify the machines are still running the expected versions. If a check fails, we can alert to make sure the docs get updated.
These are just a couple of idea, but I'd like to discuss if there are other viable options too.
@DarrenEastman @erushton @akohlbecker let me know your thoughts. I'm happy to get this going, but I want to make sure we're aligned on the approach, thanks!