Skip to content

ci: iOS on hosted macOS, Android on home-cluster runners - #1

Open
Q00 wants to merge 5 commits into
mainfrom
ci/ios-android-builds
Open

Q00 wants to merge 5 commits into
mainfrom
ci/ios-android-builds

Conversation

@Q00

@Q00 Q00 commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Adds CI for both platforms.

iOS (ios.yml): runs on GitHub-hosted macos-15. iOS needs Xcode, which runs only on macOS, and MeshKit imports CryptoKit, which has no Linux build, so it cannot run on a Linux machine. Hosted macOS minutes are free for public repos, and these jobs are safe to run on pull requests.

  • swift build + swift test of the MeshKit package
  • HermesChat, MintNotes and DailyMart built for the iOS Simulator, unsigned

Android (android.yml): runs on the home cluster's self-hosted runners.

  • jvm-core runs on [self-hosted, linux, omarchy]: gradle :meshkit-core:test
  • android runs on [self-hosted, linux, android]: gradle build, which includes meshkit-transport-intent (compileSdk 36). It runs on the Windows machine's WSL, with the SDK installed by edith/deploy/ci/setup-android-sdk.sh.
  • It never runs on pull_request, because a fork could change the workflow and run code on our runners. A push needs write access, so a push to any branch may use the runners. The repo is also set to require approval for workflows from all outside contributors.

The android job stays queued until the Windows runner is online.

🤖 Generated with Claude Code

Q00 and others added 5 commits November 14, 2026 17:04
- ios.yml: MeshKit package build+test and the three sample apps (unsigned,
  iOS Simulator) on GitHub-hosted macOS; iOS needs Xcode and MeshKit imports
  CryptoKit, so it cannot build on Linux
- android.yml: meshkit-core on the Omarchy runner, the Android library on the
  Windows/WSL runner with the Android SDK; never on pull_request (public repo,
  self-hosted runners)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kotlin("jvm") is loaded by the root build, so kotlin("android") in
meshkit-transport-intent resolved against a classloader without the Android
Gradle Plugin and failed with BaseVariant missing. Declaring both plugins at the
root with apply false puts them in one classloader. Only visible when an Android
SDK is present (settings.gradle.kts includes the module only then).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
meshkit-transport-intent depends on androidx.activity; AGP refuses the release
build without android.useAndroidX=true.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

1 participant