Repository navigation
feat(cloud): queue builds within saved server and plan allowances - #1142
Closed
Hydralerne wants to merge 2 commits into
Closed
Hydralerne wants to merge 2 commits into
Hydralerne wants to merge 2 commits into
Conversation
This was referenced Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded by combined PR #1148. This branch is preserved in the combined history. The complete migration sequence and review fixes are included there; all 15 combined CI checks pass. Merge #1148 instead of this individual draft.
Cloud builds currently share an exclusive workspace operation, and the recovered build admission work was never published. This change adds a durable FIFO queue, measured resource admission, and execution ownership so different projects can build concurrently within a managed server's saved allowance. Same-project work, maintenance and backup preparation keep their existing ownership barriers.
New offers use version 11 with explicit project, service and concurrent-build allowances. Existing paid offers retain their saved limits. The dashboard shows queue position and actionable billing recovery; traffic allowances and egress charging are unchanged.
Dependency and rollout
Targets
feat/openship-actions(#1116), not main. It supplies the missing0182_cloud_build_activityand0183_cloud_build_exclusive_preparationmigrations and inserts them before Actions migrations 0184–0186. Merge this into #1116 before releasing Actions; do not deploy an incomplete migration journal. This avoids publishing the already-reviewed Actions feature a second time.Mixed controllers with older active builds require draining or backfilling the shared admission barrier as documented in
docs/cloud-build-activity.md. Docker-owned worker cleanup is covered with mocks; this recovery did not deploy or crash a live Cloud workspace.Validation
Full combined
bun run test --continue=always: 11 workspace suites passed, including 8,912 API tests. The combined stack was checked against current main.772 focused tests covering queue admission, capacity, cancellation, recovery, saved service quotas, pricing, and UI recovery.
Five concurrency tests passed against a fresh, disposable PostgreSQL cluster; migration-upgrade preservation also passed.
108 billing/resource/API–SDK tests and 68 billing UI tests passed after updating stale offer-version expectations. Coverage preserves legacy unlimited terms while rejecting overflow on current offers.
API, dashboard and generated website TypeScript checks passed. Public SDK/CLI build and documentation checks passed.
Structured error boundaries audited; new TypeScript and Markdown files formatted.
Recovered from the shared development worktree into an isolated branch. The original uncommitted work remains intact. Kept draft for review of the plan and rollout changes.