Repository navigation
ci: move native SDK quality checks to self-hosted runners - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The native SDK Quality workflow still used GitHub-hosted machines. Run its full contract on the existing
1msg-ci-heavypool inside a digest-pinned Ubuntu 24.04 container; the required aggregate runs on1msg-ciand fails on skipped/cancelled/failed contracts.Preserve the existing Node 26.13.1, pnpm 12.18.0, Java 24 and native toolchain versions, frozen dependencies, generator replay, negative checks and native tests. OS package installation stays inside the disposable container, pnpm has a unique per-job path, and checkout ownership is restored for later jobs. No SDK runtime or generated source changes.
Only repository pushes and manual dispatch schedule the shared runner pool. Same-repository PRs receive required checks on their head SHA; maintainers must review fork contributions and copy them to an owned branch. Repository settings also require approval from all external contributors. There is no pull_request_target execution path.
Validation: actionlint, Prettier and git diff --check pass locally. The full self-hosted Quality run passed: native SDK build/ctest, install and external consumer build/ctest, generator replay/negative checks, static/unused/duplicate gates and quality fixtures. Contract ran on monitoring-2; required aggregate on monitoring-1. Container cleanup completed successfully.