ci(kmp): add remote HTTP build cache and Konan toolchain caching#1016
Conversation
- Add packages/kmp/gradle/build-cache.settings.gradle (shared remote HTTP build cache), applied from packages/kmp/settings.gradle.kts and configured from the GRADLE_CACHE_URL / GRADLE_CACHE_USERNAME / GRADLE_CACHE_PASSWORD secrets. Push is enabled only when credentials are present, so fork PRs are pull-only and cannot poison the cache. - Pass GRADLE_CACHE_* to the KMP CI, snapshot, and publish workflows. - Cache ~/.konan across those workflows — each compiles all 14 KMP targets (including native) on macOS from a cold Konan today. Part of the Meshtastic KMP library standard alignment (CI caching). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest Buf updates on your PR. Results from workflow pull-request / build (pull_request).
|
Addresses CodeRabbit review of the shared build-cache script: - Drop allowInsecureProtocol/allowUntrustedServer — the cache server presents a valid public TLS cert, so enforce HTTPS + certificate validation. - Write to the cache only on trusted events (push/merge_group/local) with credentials present, so pull_request runs stay pull-only and cannot poison the cache. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2 participants
Summary
Adds Gradle build-cache reuse for the
packages/kmpartifact, which compiles all 14 KMP targets (incl. native) on macOS in every KMP workflow.What changed
packages/kmp/gradle/build-cache.settings.gradle(new): shared remote HTTP build cache, applied frompackages/kmp/settings.gradle.kts, configured fromGRADLE_CACHE_URL/GRADLE_CACHE_USERNAME/GRADLE_CACHE_PASSWORD(CI secrets; nothing hardcoded). Push only with credentials → fork PRs are pull-only and can't poison the cache.~/.konancaching (actions/cache@v6) added tokmp-pull-request.yml,snapshot-kmp.yml, and both jobs ofpublish-kmp.yml— keyed onbuild.gradle.kts+ wrapper. Today every run re-downloads the Kotlin/Native toolchain from cold.GRADLE_CACHE_*env wired into all three KMP workflows.Required repo secrets (please add)
GRADLE_CACHE_URL,GRADLE_CACHE_USERNAME(meshtastic),GRADLE_CACHE_PASSWORD. Absent them, the remote cache disables itself (local + Konan cache still work) — CI never breaks.Notes
actionlintclean on all three workflows. Only touches the KMP packaging/CI — no.protoor generated-code changes.🤖 Generated with Claude Code