In the previous two posts I show you how to create the project structure and create a basic team build for your CRM solution artifacts. In this final installment I go about setting up a release definition for the build that we created.
Let's start off by creating a new release by navigating to the Build and Release > Release in your team project.
Select the Empty template option and click the next button.
Set the following arguments for the script - notice that the previously defined variables DevDeployLogin and DevDeployPassword being used as part of the script.
-serverUrl "https://servername.crm6.dynamics.com" -username "$(DevDeployLogin)" -password "$(DevDeployPassword)" -solutionName "Demo.AlphaSolution" -publishChanges -activatePlugins
Expand the Advanced tab and click the ellipsis button on the Working Folder field. Set the working folder to the Nullfactory.Xrm.Tooling\Scripts folder on the resulting dialog. I do this in order to minimize the chance of encountering any long file path issues.
Now that everything is setup, time to test out our new release definition. Let's queue a new release.
Ensure that the release is being deployed and that it completed successfully.
That's it folks. That's the end of the three part series showing how to setup a project structure, configure a build and finally release a source-controlled CRM solution.