3

We have a SharePoint 2013 application which has 11 WSP and only one of these WSPs has 12 features. The overall solution works fine, all with good performance. However, the issue is that when we do the deployment it takes almost 4-5 Hours to complete deployment.

We are using best practice for deployments, like Settings file, Template file, and webconfigupdate files. And we are using PowerShell to do the deployment. This long deployment time is causing us problem whenever we have more releases/deployments, because our servers are shared with other applications and deployment for our application causes downtime for others.

It would be great if the experts here could suggest what can be done to reduce the deployment time.

Thanks in advance.

Improve this question
  • Do you have any info as to why it is taking 4-5 hours? – Sudhakar Oct 21 '16 at 13:15
  • 2
    Impossible to say based on what you've provided, but my guess is that your solution is poorly architected. Do you really need to push all 11 WSPs every time you update? If so, that's a sign of poor architecture. – Derek Gusoff Oct 21 '16 at 13:40
-1

Solution Deployment is not a quick job as per my experience.it depends multiple factor

  • Number of solution you deploying
  • Number of Web Application in the farm
  • Number of SharePoint servers in the farm
  • Resources available for the deployment

Please check the resource while deployment under process

Improve this answer

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.