Working with Resources

You are viewing an old version (v. 2) of this page.
The latest version is v. 5, last edited on Sep 15, 2011 (view differences | )
<< View previous version | view page history | view next version >>

Resource means any physical or virtual component of limited availability within the grid, and is provided by grid node. A build step can declare to require certain resources to run. If some nodes are found with desired resources, the step will run on the fastest node; otherwise, the step will wait until a node with free resource is available. This way, the resource contention problem between builds and steps can be solved efficiently.

For instance, we can define a CPU resource representing all CPUs of all agents in the grid, and declare that master step of the build requires the CPU resource. This guarantees that a CPU will run one and only one build. If CPU resource is currently used up, new build requests will wait until there is a free one. Another example is that you have a single deployment machine in your grid, and only one deployment step can deploy to that machine in the same time. In this case, you may define a deployment resource corresponding to that machine, and for each deploy step, define it to require the deployment resource.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.