How the Probo.CI Build Queue Works

When multiple builds are triggered at the same time, they are managed through an automated queue system to ensure fair, orderly execution within the limits of your plan.

1. What Triggers Queuing

   When a build is submitted, Probo.CI checks two concurrency limits before running it:

   1.1 System-Wide Limit. A global ceiling on concurrent builds running across the entire platform. This is managed by infrastructure and is transparent to end users.

   1.2 Organization Limit. A per-organization limit based on your subscription plan. This controls how many builds your organization can run simultaneously. If your organization’s concurrent build slots are all occupied, any new builds are held in queue until a slot becomes available.

   If either limit is reached at the time of submission, the build is placed in the queue automatically. No action is required on your part.

   It IS possible for your queue to not be full and a build still be queued in the system queue is at capacity.

2. Queue Ordering

   Builds are queued and executed in first-in, first-out (FIFO) order, based on the time they were submitted. There is no priority system - builds run in the order they arrive. This applies equally across all repositories within your organization amd globally on the platform.

3. Automatic Dequeuing

   When a running build finishes, Probo.CI automatically checks the queue and submits the next build for your organization, provided a slot is available. This process is fully automatic - you do not need to manually trigger or release queued builds.

   The full concurrency check is re-run at dequeue time, so a queued build only proceeds when a slot is genuinely available.

4. Queued Builds Do Not Expire

   There is no timeout on queued builds. A build will remain in the queue until a slot opens and it can be submitted to the container environment. If you believe a build is stuck in queue unexpectedly, please contact support at hello@probo.ci.

5. Cancelling Queued Builds

   Individual queued builds can be queued by deleting the build using the trash can icon on the build page. Contact us at hello@probo.ci if you’re interested in more queue space without upgrading plans.

6. Increasing Your Concurrent Build Limit

   Your concurrent build limit is determined by your subscription plan. If your team regularly experiences queued builds and you need more throughput, upgrading your plan will increase the number of builds your organization can run simultaneously. Visit our pricing page to compare plans, or contact us at hello@probo.ci to discuss your needs.

7. Questions

   If you have questions about the queue system or your organization’s build limits, please reach out to us at hello@probo.ci.