Exclusive Deployment

Version 4 by Robin Shen
on Sep 18, 2011 14:37.

<< Changes from 3 to 4

compared with

Current by Robin Shen
on Sep 18, 2011 14:48.

Key

These lines were removed. This word was removed.

These lines were added. This word was added.

There are 1 changes. View first change.

		h1. 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.

		h1. Demonstration
		# Visit the [demo project\|http://demo.pmease.com/overview/105], and hit the run button to trigger all children configurations concurrently.
		# Check latest build of [child project1\|http://demo.pmease.com/build/106.latest] and [child project2\|http://demo.pmease.com/build/107.latest] respectively: only _deploy_ step of the one build will run, another will be put into wait state until current running deploy step finishes.

		h1. Resolution
		# Switch to [resources tab\|http://demo.pmease.com/grid/resources] and a resource named "Deployment Environment" is defined with only one agent providing the resource.
		# Switch to [steps definition\|http://demo.pmease.com/settings/101/steps] 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_.
		# 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.
		# Switch to steps definition of [child project1\|http://demo.pmease.com/settings/106/steps] and [child project2\|http://demo.pmease.com/settings/107/steps], and check definition of step _deploy_. The node selection property is set to run on the node with resource _Deployment Environment_.