Exclusive Deployment

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

Situation

Assume there are only one machine for deployment. Set up the build so that only one deployment step can run on the deployment machine even if multiple builds try to deploy.

Demonstration

  1. Visit the demo project, and hit the run button to trigger all children configurations concurrently.
  2. Check latest build of child project1 and child project2 respectively: only deploy step of the one build will run, another will be put into wait state until current running deploy step finishes.

Resolution

  1. Switch to resources tab and a resource named "Deployment Environment" is defined with only one agent providing the resource.
  2. Switch to steps definition of the demo project, and check definition of step deploy. The node selection property is set to run on the node with resource Deployment Environment.
  3. This also holds true for builds from different configurations as long as their deploy step is defined to run on node with the Deployment Environment resource.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.