Skip to content

ci: run GitHub Actions on Blacksmith runners#1139

Open
busbyk wants to merge 2 commits into
mainfrom
busbyk/blacksmith-runners
Open

ci: run GitHub Actions on Blacksmith runners#1139
busbyk wants to merge 2 commits into
mainfrom
busbyk/blacksmith-runners

Conversation

@busbyk

@busbyk busbyk commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Description

Runs our GitHub Actions CI on Blacksmith managed runners instead of GitHub-hosted ubuntu-latest. Blacksmith runners are drop-in replacements that give us faster queue times and build caching at a lower per-minute cost. This mirrors the same change we made in the trashlane repo.

Related Issues

N/A

Key Changes

  • Swapped runs-on: ubuntu-latestruns-on: blacksmith-2vcpu-ubuntu-2404 across all 17 jobs in 9 workflow files: ci.yaml, development.yaml, production.yaml, preview.yaml, cleanup.yaml, claude.yml, dependabot-auto-format.yml, post-release.yml, sync-prod-to-dev.yml.
  • Started at the 2vcpu tier (Blacksmith's cheapest) to validate real speedups before paying for larger sizes.
  • No other workflow changes — no Blacksmith-specific caching actions or config, matching the minimal trashlane setup. The e2e job's container: step is untouched (Blacksmith supports container jobs).

How to test

  • The Blacksmith GitHub App is installed on the NWACus org, so jobs carrying the blacksmith-* label pick up managed runners automatically.
  • Confirm the CI checks on this PR complete green — the Actions job logs will show a Blacksmith runner rather than a GitHub-hosted one.
  • Compare job durations against recent ubuntu-latest runs on main via the Blacksmith dashboard.

Screenshots / Demo video

N/A

Migration Explanation

N/A — no database migration.

Future enhancements / Questions

  • If build and e2e (which run next build + Playwright) turn out to be CPU-bound at 2vcpu, bump just those two jobs to 4vcpu while leaving the lighter jobs (lint, prettier, test, drift, fallow) at 2vcpu.

🤖 Generated with Claude Code


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.

Swap all 17 jobs across 9 workflows from ubuntu-latest to blacksmith-2vcpu-ubuntu-2404 to run CI on Blacksmith's managed runners for faster queue times and caching at lower cost. Matches the minimal trashlane setup; no other workflow changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Preview deployment: https://busbykxblacksmith-runners.preview.avy-fx.org

The preview deploy seeds a fresh Turso DB via pnpm seed:standalone, which issues thousands of per-row network round-trips. That latency-bound stream reproducibly kills Blacksmith runners mid-seed (2/2 attempts). Revert just this workflow to ubuntu-latest where seed completes (~289s); everything else stays on Blacksmith. Durable fix (seed local -> bulk import to Turso) tracked in #1143.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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