I have updated CRMCommandLineUtilities to support CRM 2013 Online deployment automation with TFS. This was a codeplex project by Ryan Corrigal which helped me a lot to implement CRM 2011 on premises automated deployments with TFS.
You can find the updated command line utilities @ http://sdrv.ms/1h9lzJW (Code is not yet perfect since some hardcoded values for timeouts.)
To use this easily with TFS build, in the LabDefaultTemplate deployment step, use the command
cmd /c $(BuildLocation)\Deploy_QA.bat $(BuildLocation)
Or if you are using TFS 2013, you can directly execute PowerShell script from the build to invoke command line utilities for CRM.
More information on Zip Files with builds and Deployment Scripts are in my previous posts
Useful Powershell Scripts and .bat files are here
http://sdrv.ms/1bKdCmM, http://sdrv.ms/1bKdTpF, http://sdrv.ms/1bKdZh0
I will update more usage info in future posts. The final goal would be to achieve something similar to below.
The error messages displayed in the build screenshot above are handled and they are coming when verifying the async process status, due to CRM online service sql timeouts. But this is ok since the import continues and finally status check confirms 30 for process succeeded. Immediately afterwards Publish attempt may fail and I have introduced retry mechanism to make sure publish successful.
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Dynamic block allows to create nested multi level block structures in terraform code. Conditional usage of such blocks are really useful in...
-
In Azure DevOps YAML pipelines there are several functions available for you to use. replace is such a useful function, which you can use t...
-
We have discueed, that we have to use an environment variable to handle input parameter default values, if we are using trigger for workflo...
-
Adding Azure Container Registry (ACR) service connection to Azure DevOps is really simple as described in " Create Service Connection ...
-
Some times a silly mistake can waste lot of time of a developer. The exception “System.IO.IOException: The response ended prematurely.” whil...
No comments:
Post a Comment