Skip to main content

Azure Pipelines with Sitecore TDS Project

Azure DevOps with Sitecore TDS Project

Azure DevOps provides Build and Release Pipeline feature for Continuous Integration and Continuous Deployment.

Before TFS 2017/VSTS/Azure DevOps, we used to have had Build Server to support deployment where we had all required binaries. But since when Hosted agent has been launched we need to setup Build Pipeline this way so that Hosted agent could build our solution.

We should add all required dlls reference from NuGet package so that Hosted agent could restore from NuGet library while build the solution. This is good for normal ASP.NET MVC project but how TDS dependency would be resolved in Sitecore Project with TDS on Build Server.

How to Set Up Azure Build Pipeline for Sitecore TDS

Prerequisites: TDS version should be minimum 5.8.0.6
  • Open your Sitecore Project.
  • Open Package manager Console
  • Check your installed TDS version and Execute below command
PM> Install-Package HedgehogDevelopment.TDS -Version x.x.x.x 
  • Above step will installed TDS binaries through NuGet library what will remove the dependency of TDS binaries on Build Server because it will resolved through NuGet now.
  • Open your Sitecore TDS Project properties and Select proper option as per your requirements under WebDeploy package options.

  • If you have more than one TDS project then enable in anyone else it will create N number of times where N is your TDS Project count.
  • If you want to enable in all then you would have to pass additional parameter in Build Pipeline.
  • Deploy latest HedgehogDevelopment.SitecoreProject.Service.dll to your Sitecore Environment.
  • Check latest files are in _DEV Folder or not in your Sitecore Environment.
  • Go to Azure Build Pipeline and Create two variables to build TDS project.

  • Add above two variables reference in your build pipeline.
  • Modify Copy Files TasK in Build Pipeline so that only WebDeploy package could upload in artifacts directory.

  • This way you would have correct .wdp package with .ps1.

How to Set Up Release Pipeline

Release Deployment is easy and follow the steps as per here.




Comments

Popular posts from this blog

How to Install Docker Desktop 2.3.0.4 on Windows

There are two types of installer one is Community and other is Enterprise. Here I am discussing how we can install Docker Desktop Community version on Windows 10. Please find here latest stable version of Docker and run installer. Prerequisites Hyper-v manager should be installed and enable. If not installed then run below command through Windows Powershell using Admin Privileges. Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All Enable-WindowsOptionalFeature -Online -FeatureName Containers -All Server Service should be started and enabled. If this is disabled then enable the service and start using admin Privileges. Errors during Direct Installation If you would try to run installer directly, you would get below error while installing Docker Desktop it means that Server Service is not started on your machine. So, please Restart Server Service. [22:51:02.244] [InstallHandler] No installation found [22:51:02.246] [InstallHandler] Using embedded package [22:51:...

How to Convert Azure Pipelines to YAML Pipeline

What is Azure YAML Pipeline? YAML is a new markup language what provides single unified experience to developers to manage Continuous Integration and Continuous Delivery at a single place. How to Convert Azure Build Pipeline to YAML Pipeline Go to Build Pipeline to which you want to convert. Get your YAML text as per below image and copy to notepad. You would also noticed that there would be some warnings at top. We need to define variables. Create a New Pipeline. Select Azure Git Repository. Select ASP.NET Template. Default YAML pipeline would be like below # ASP.NET # Build and test ASP.NET projects. # Add steps that publish symbols, save build artifacts, deploy, and more: # https://docs.microsoft.com/azure/devops/pipelines/apps/aspnet/build-aspnet-4 trigger : -  master pool :    vmImage :  'windows-latest' variables :    solution :  '**/*.sln'    buil...