0

We are deploying our Sitecore 9.2 app using Azure DevOps. More specifically we use WebDeploy and deployment slots and have noticed the following behaviour:

  • deployment to deployment slot takes an extended time (25+ mins), if the target slot has a different code-branch deployed

  • if we re-deploy to the same slot, without having swapped the target slot into production, the following deployment takes a short time(5-8 mins)

  • the majority of the files (all the sitecore files) have not changed between deployments

We can see that when our deployment takes a short time, there are few files updated and when deployment takes a long time, all the files (9000+) are updated. We are puzzled by the fact, that the Sitecore files are updated, since they are the only thing that does not change.

We have tried using webdeploy with -usechecksum parameter and without, but it does not result in any noticeable difference.

We also tried to deploy the application, without using deployment slots and that is always fast (5-7 mins).

Here is a screenshot of our deployment step: (Azure App Service deploy task v.4) enter image description here

Is there a way to constantly achieve quick deployment times and use deployment slots?

  • Can you post your msdeploy command in full? – Mark Gibbons Feb 17 at 11:43
  • @MarkGibbons Added screenshot of deployment step in full – Hos Feb 17 at 18:21
0

Have you confirmed you have 'ignore app_data' checked? You don't want to Web Deploy sync over that folder if you can avoid it as Azure puts hundreds of meta files into folders in there which would then all be removed and it will take some time... :P

If you deploy once and it takes ages, but then re-deploy and it's quicker it could just be that there are fewer of Azure's files to be removed with web deploy on the 2nd deployment?

| improve this answer | |
  • I can confirm that I have enabled "Exclude files from the AppData folder". Also, I am wondering why Webdeploy wants to update my Sitecore files since they are not changed between deployments – Hos Feb 16 at 18:34
  • @Hos I think if you've got a new package, it's likely the file time stamps will be different and that's what web deploy uses by default to identify changes to files. This is a pretty decent description of how to configure things if this is your issue: dotnetcatch.com/2016/06/03/… – Dave Goosem Feb 18 at 4:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.