Build Concurrency and Queuing

Version 7 by Robin Shen
on Sep 18, 2011 12:48.

<< Changes from 6 to 7

compared with

Version 8 by Robin Shen
on Sep 18, 2011 13:06.

Changes from 8 to 9 >>

Key

These lines were removed. This word was removed.

These lines were added. This word was added.

There are 1 changes. View first change.

-As explained in [working with resources] section, one can define resources in grid page to control how many steps can run concurrently. Specifically, if resource requirement is applied to master step, the whole build will be put into waiting state if the requirement is not satisfied. You may also refer to [the resource management tutorial|resource management] on how to control the build concurrency.
-h1.
+As explained in [working with resources] section, one can define resources in grid page to control how many steps can run concurrently. Specifically, if resource requirement is applied to master step, the whole build will be queued when the requirement is not satisfied. You may also refer to [the resource management tutorial|resource management] on how to control the build concurrency.
+h1. Concurrency of Builds of the Same Configuration
+Concurrency of builds of the same configuration is also affected by workspaces. QuickBuild guarantees that a workspace is only used by one build at a time. Assume that _step1_ and _step2_ belongs to _build1_ and _build2_ respectively. If _step1_ and _step2_ both matches the single same node, the second step will wait until the first step finishes. Specifically if the waiting step is of master step, the whole build will be put into queue for waiting.