Skip to content

ci(cloud-cf-deploy): configurable migrate-db runner to unblock prod when hosted queue jams #11449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NubsCarson merged 1 commit into from
Jul 2, 2026
Merged

ci(cloud-cf-deploy): configurable migrate-db runner to unblock prod when hosted queue jams #11449

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions .github/workflows/cloud-cf-deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,17 @@ jobs:
migrate-db:
name: Run Database Migrations
if: github.event_name != 'pull_request'
# GitHub-hosted on purpose: migrations must not inherit the shared
# self-hosted deploy fleet's failure modes (mirrors cloud-deploy-backend).
runs-on: ubuntu-latest
# GitHub-hosted by DEFAULT so migrations don't inherit the shared
# self-hosted deploy fleet's heavy-checkout failure modes (mirrors
# cloud-deploy-backend). But the hosted ubuntu-latest pool periodically
# backs up for hours (org-wide zombie-freeze), and since every deploy job
# `needs: migrate-db`, a starved hosted queue blocks ALL prod deploys even
# while the self-hosted robot pool sits idle. CLOUD_CF_MIGRATE_RUNNER_JSON
# lets ops fail migrations over to the robot pool (e.g.
# ["self-hosted","Linux","X64","hetzner-robot"]) when hosted is jammed;
# migrate is a light `bun install` + `db:cloud:migrate`, not the heavy
# working-tree materialization that motivated keeping deploys off-hosted.
runs-on: ${{ fromJSON(vars.CLOUD_CF_MIGRATE_RUNNER_JSON || '["ubuntu-latest"]') }}
# Job-level concurrency groups are repo-wide, so this serializes against
# cloud-deploy-backend's migrate-db too: overlapping triggers (a develop
# push fires both workflows) can never run the migrator concurrently
Expand Down
Loading