syntaqxSelf-hosted runners: a workspace on hold registers none, and a free workspace runs 4 of its workflow jobs on them at once. Runner registration had no billing check, and jobs on self-hosted runners skipped the workspace's concurrency limit, so a free workspace could run any number of jobs (each uploading artifacts and cache and writing logs) on runners of its own. Making a registration token now asks billing for the workspace's standing and refuses one while g1t staff hold it (Entitlements gains held). When a runner looks for work and its workspace already has FREE_SELF_HOSTED_JOBS (4, a wrangler var; 0 is no cap) jobs going on its runners, billing is asked whether it has the plan; without it, the workflow jobs wait until one finishes. Billing is asked only at the cap, so a runner's poll stays cheap, and when billing does not answer jobs go ahead. The self-hosted runners guide says so.f1e1810History
- ..
- abuse.tsx
- agents.tsx
- aliases.tsx
- audit.tsx
- costs-bill.tsx
- costs.tsx
- credits.tsx
- deleted-accounts.tsx
- deleted-workspaces.tsx
- enterprise.tsx
- enterprises.tsx
- incident-new.tsx
- incident-postmortem.tsx
- incident.tsx
- incidents.tsx
- invites.tsx
- invoices.tsx
- legacy-accounts.tsx
- maintenance-new.tsx
- maintenance.tsx
- new-enterprise.tsx
- overages.tsx
- overview.tsx
- reach-out.tsx
- requests.tsx
- soon.tsx
- stripe.tsx
- timezone.tsx
- user.tsx
- velocity.tsx
- workspace.tsx
- workspaces.tsx