Skip to content

ci: run heavy CI and publish builds on the self-hosted agentos-builder pool#1603

Open
NathanFlurry wants to merge 1 commit into
mainfrom
ci-self-hosted-runners
Open

ci: run heavy CI and publish builds on the self-hosted agentos-builder pool#1603
NathanFlurry wants to merge 1 commit into
mainfrom
ci-self-hosted-runners

Conversation

@NathanFlurry

Copy link
Copy Markdown
Member
  • ci.yml and the x64 publish build run on [self-hosted, agentos-builder] instead of GitHub-hosted runners, sharing the warm secure-exec build cache (persistent target/, shared CARGO_HOME + sccache) with secure-exec CI
  • Drop the redundant GHA rust-cache / pnpm-cache steps (the persistent runner disk is the cache)
  • arm64 publish stays on GitHub ARM runners (the self-hosted pool is x64)

@railway-app railway-app Bot temporarily deployed to agentos / agentos-pr-1603 July 4, 2026 00:01 Destroyed
@NathanFlurry NathanFlurry force-pushed the ci-self-hosted-runners branch from 8a14562 to a7628b3 Compare July 4, 2026 00:15
@railway-app railway-app Bot temporarily deployed to agentos / agentos-pr-1603 July 4, 2026 00:15 Destroyed
@railway-app

railway-app Bot commented Jul 4, 2026

Copy link
Copy Markdown

🚅 Deployed to the agentos-pr-1603 environment in agentos

Service Status Web Updated (UTC)
agentos 😴 Sleeping (View Logs) Web Jul 4, 2026 at 1:37 am

🚅 Environment agentos-pr-1603 in rivet-frontend has no services deployed.

…rust job

- checks (GitHub-hosted): TypeScript/boundary/metadata checks + rustfmt — small,
  dynamic, no heavy cargo compile.
- rust (self-hosted agentos-builder pool): prepare-build + clippy + the Rust test
  suites + sidecar-heavy e2e — CPU/mem intensive and cache-bound.
- x64 publish build also runs on the self-hosted pool; arm64 stays on GitHub.
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