Skip to content

ci: prefer self-hosted runners with GitHub-hosted fallback - #13

Merged
br4vesirrobin merged 1 commit into
mainfrom
chore/self-hosted-wrapper
Jun 8, 2026
Merged

ci: prefer self-hosted runners with GitHub-hosted fallback#13
br4vesirrobin merged 1 commit into
mainfrom
chore/self-hosted-wrapper

Conversation

@br4vesirrobin

Copy link
Copy Markdown
Collaborator

Summary

Routes ci.yml (elixir / node / python) to self-hosted runners with automatic GitHub-hosted fallback.

  • Each canonical job now needs a continue-on-error self-hosted leg and only re-runs the work on GitHub-hosted runners when the self-hosted leg did not pass (outputs.passed != 'true').
  • Node/archgate leg routes to [self-hosted, macOS] because archgate ships no linux/arm64 binary; Elixir and Python legs run on [self-hosted, ubuntu-latest].
  • Original status-check contexts preserved exactly: Elixir tests, Node.js tests & ADR check, Python pipeline-runner, All checks passed.

Part of r3dlex/github-runners-for-repo#12

Wrap elixir/node/python jobs in the self-hosted-preferred pattern:
each canonical job now depends on a continue-on-error self-hosted leg
and only re-runs on GitHub-hosted runners when the self-hosted leg
did not pass. The Node/archgate leg routes to the macOS self-hosted
runner (archgate has no linux/arm64 binary). Original check-name
contexts (Elixir tests, Node.js tests & ADR check, Python
pipeline-runner, All checks passed) are preserved exactly.

Part of r3dlex/github-runners-for-repo#12

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@br4vesirrobin
br4vesirrobin merged commit 4ec2ad6 into main Jun 8, 2026
6 of 7 checks passed
@br4vesirrobin
br4vesirrobin deleted the chore/self-hosted-wrapper branch June 8, 2026 12:49
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