Public: anyone can read this; nobody can change it.

azure-gate: allow 2 concurrent runs (per-run concurrency group) #147

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

Lets two azure-gate runs go at once (e.g. you + Ben practicing) instead of serializing them. Switches the concurrency group from a shared azure-gate to per-run azure-gate-${{ github.runid }}; the real cap becomes the vxrail-coldstart runner's 2 slots.

Notes

shipped merged

opened this view on origin

Lets two azure-gate runs go at once (e.g. you + Ben practicing) instead of serializing them. Switches the concurrency group from a shared azure-gate to per-run azure-gate-${{ github.run_id }}; the real cap becomes the vxrail-coldstart runner's 2 slots. Safe because each run is fully isolated — its own mitosis-gate-<run> RG, and in aks its own DNS sub-zone — so concurrent runs never collide on Azure. cancel-in-progress stays false (a cancelled deploy would orphan a paid RG). Noted: two concurrent aks runs need 16 vCPU vs the family's 10, so raise quota before aks+aks (vms+vms or vms+aks are fine).

🤖 Generated with Claude Code

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs