Skip to content

ci: use the pigma self-hosted runner - #33

Merged
recrack merged 1 commit into
masterfrom
codex/pigma-self-hosted-ci-20261021
Oct 21, 2026
Merged

recrack merged 1 commit into
masterfrom
codex/pigma-self-hosted-ci-20261021

Conversation

@recrack

@recrack recrack commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Summary

- runs-on: ubuntu-latest
+ runs-on: [self-hosted, Linux, ARM64, pigma-<repository>]

Route compatible jobs to the repository-specific pigma runner. Preserve workflow triggers, tests, secrets, permissions, and deployment commands. External fork PRs in public repositories retain hosted isolation.

Evidence

  • Before: compatible jobs request hosted Ubuntu runners.
    After: YAML parses and a structural comparison verifies that only runner routing changed. The dedicated runner is registered on pigma; CI results are reported on this PR.

Unchanged jobs needing another environment:

  • test: macos-15

Merge Danger

Door: two-way

Blast Radius: CI

Migration is limited to execution placement. The shared runner slice caps total new CI CPU and memory; individual repository containers have no host data or Docker socket mounted.

@recrack
recrack merged commit d221ae4 into master Oct 21, 2026
3 checks passed
@recrack
recrack deleted the codex/pigma-self-hosted-ci-20261021 branch October 21, 2026 05:33
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