To define a release template Click New on Configure Apps tab of the VS Release Management Client.
![001 001](http://lh3.ggpht.com/-DMaVn-w52zU/VElWeKcFBxI/AAAAAAAADD0/OssS0gFwOPY/001_thumb%25255B1%25255D.png?imgmax=800)
Provide a name for the release template
![002 002](http://lh6.ggpht.com/--nZmXI6XuCI/VElWfyJJJ8I/AAAAAAAADEE/rCY88BGHeJk/002_thumb%25255B1%25255D.png?imgmax=800)
Select the Release Path
![003 003](http://lh4.ggpht.com/-5BNWgEkqwHY/VElWmnbEY3I/AAAAAAAADEU/-CnFPY1mmcQ/003_thumb%25255B1%25255D.png?imgmax=800)
Since the TFS is integrated with the release management server, we can select a build definition that can be used to obtain the deployment package/payload.
Select the Team Project
![004 004](http://lh4.ggpht.com/-GHtLr6hBJOE/VElWoq6Ec2I/AAAAAAAADEk/NvmyuEbz2Hs/004_thumb%25255B1%25255D.png?imgmax=800)
Then select the build definition which is generating output.
![005 005](http://lh6.ggpht.com/-Qg-14puwi98/VElWsQy__yI/AAAAAAAADE0/XDHd9n9kErY/005_thumb%25255B1%25255D.png?imgmax=800)
The purpose of “Can Trigger a Release from a Build” is to allow triggering a Release from the TFS build. But this requires some additional steps in Build templates and definitions which I will explain in a future post.
Security tab can be used to configure following permissions for Release Management users or groups.
![006 006](http://lh6.ggpht.com/-M02K4imgez0/VElWtL8oPdI/AAAAAAAADE8/Bhyup6eO2jY/006_thumb%25255B1%25255D.png?imgmax=800)
View – Can view this Release Template |
Edit – Can edit this Release Template |
Can Release – Can trigger a release using this Release Template |
Manage Security – Can edit permissions for this Release Template |
![007 007](http://lh6.ggpht.com/-rYR2js4aN2Q/VElWu8FhiWI/AAAAAAAADFM/36D3w5dUreg/007_thumb%25255B2%25255D.png?imgmax=800)
The above shown window can be opened by clicking the properties link below and edit the properties of release template after creation.
![008 008](http://lh3.ggpht.com/-Z10R6msLqk8/VElW1i3Dh_I/AAAAAAAADFc/YGvQ5jxexqw/008_thumb%25255B1%25255D.png?imgmax=800)
Since our release path had three stages DevInt, QA and Prod we can define a deployment sequence for each of these stages.
![009 009](http://lh5.ggpht.com/-KeHmXSHDuvQ/VElW2-Qg8SI/AAAAAAAADFs/o3LM_RTX_CI/009_thumb%25255B1%25255D.png?imgmax=800)
You can see the tags we have defined in each environment appears in left toolbox under tags. Since we are using the same server machine for this demo there is only one and same server in each stage.
![010 010](http://lh5.ggpht.com/-hvJrCt4peLw/VElW9nitVNI/AAAAAAAADF8/2H1Kf1BgOfk/010_thumb%25255B1%25255D.png?imgmax=800)
In the second part of this post, I will explain how to define a simple deployment sequence.