Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate client & IDE Testing on MacOS #347

Open
jwmatthews opened this issue Aug 31, 2024 · 3 comments
Open

Automate client & IDE Testing on MacOS #347

jwmatthews opened this issue Aug 31, 2024 · 3 comments

Comments

@jwmatthews
Copy link
Member

We want to enable an automated means of testing Kai Client and IDE workflows on MacOS.

Idea being to provision a Mac Desktop in AWS and automate run through of both Client and IDE workflows.

@jmontleon
Copy link
Member

It looks like we can launch macs using dedicated instances. They will be tied to our account for at least 24 hours.
https://aws.amazon.com/getting-started/hands-on/launch-connect-to-amazon-ec2-mac-instance/

We then have ssh and can enable remote destkop access if desired:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/mac-instance-launch.html

@jmontleon
Copy link
Member

We could potentially configured a dedicated host as a self-hosted runner and trigger jobs on it from GitHub:
https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#macos

@jmontleon
Copy link
Member

From looking previously at self-hosted runners I think @shawn-hurley and I found some special considerations if we take this approach.

  • We could not find a way for a job to run on both hosted and self-hosted runners we would probably want to keep mac oriented jobs separate.
  • There is no cleanup done after the test is run; GitHub hosted runners just go away, so this is taken for granted. Here we would be on the hook to clean up before/after each run adding some complexity.

@shawn-hurley might remember more, but I think these stood out as the biggest ones to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants