The Build Grid can be managed by switching to Grid tab as shown below:
QuickBuild by default assumes that all grid nodes have the same performance and distribute build tasks evenly to all matched grid nodes (controlled by node matching setting of a step). However, it is normal that some node is more powerful than other nodes and should get more loads. In this case, please edit bin/config.(bat|sh) to specify performance factor of the node. By default, all nodes have the performance factor of 10.
Node attributes can be used to filter nodes for certain steps by specifying the step property node match condition. For example, the condition node.getAttribute("os.name").startsWith("Windows") matches only agents running Windows operating system, while condition node.hasAttribute("ant") matches agents that have the attribute ant defined.
System defined attributes include all environment variables and all Java system properties.
User attributes are custom attributes that are defined by user to identify ability/environment of the node. For example, if the agent has Ant and Maven installed, you may define user attributes to reflect this installation as below:
A single unit of work running on a grid node is called a grid job. In most cases, it is just a step. A grid node may have many jobs running concurrently (for example, steps from builds of different configurations). The number of concurrent jobs is limited by node resources (such as working threads). If the resources are exhausted, newly arriving jobs will be waiting in the queue. A typical job monitoring screen looks like this: