Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…lds are already running
…instead of polling loop in build.service.ts
…ent-watch.service.ts
…eturn types are passed to frontend
859d2a5 to
b6bcfbb
Compare
…ob readiness check to check against ready property instead of active
… removed concurrency build settings
…ervice instead of polling
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
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.
This pull request introduces a new "Builds" overview page to the application, providing a global view of all build jobs across apps. It includes a new server action API for fetching and deleting builds, a client-side table UI with status badges and actions, and improved integration with build and deployment event watchers. Additionally, this PR replaces the polling mechanism for build job status with a global watch. QuickStack is now informed by k3s when a build job has completed or failed.To optimize workloads during builds, a new setting "Concurrent Builds" has been introduced, which controls how many builds can run concurrently.