1. Continuous Integration for SharePoint Solutions and Add-ins with VSTS and Azure Matthias Einig, MVP, CEO w: rencore.com | e: matthias.einig@rencore.com | t: @mattein

2. Matthias Einig matthias.einig@rencore.com www.rencore.com @mattein CEO, SharePoint MVP Munich, Germany

3. Agenda 1.Continuous Integration/Delivery 2.VS Online & Azure 3.CD for Farm/Sandboxed Solutions 4.CD for Provider Hosted Apps 5.Release Management 6.Summary

4. Continuous what? Build centralized Check Quality Continuous Integration Code Quality Build centralized Check Quality Deploy Continuous Deployment Process Quality Build centralized Check Quality Deploy Test Continuous Delivery Functional Quality

5. Why? Fail fast and early in the development process Deliver smaller increments == less defects Know exactly what is deployed Reproducable No dependency on specific people

6. Manual deployment != Fun

7. What should be included? Farm Solutions Apps Database schema C ode WSP, App, Data, PowerShell Farm / Site settings Site Structure Feature Activations … C onfiguratio n Files, List Data Taxonomies Database Content … C ontent

8. Dev Challenges Deployment of VMs time consuming, resource and performance hungry Multiple environments required (SP2010/2013/2016, CUs/Service Packs, Websites, O365 tenants, DEV/INT/ACC/PROD) Deployment/Testing requires „clean“ production- like environment VMs for different versions of the own solution(s) Deployment process complicated and error- prone

9. The solution! Source Control Workitem Tracking Project Management Automated Build Test Management Analytics … Websites Virtual Machines Storage Databases Active Directory Networks …

10. Source Control Workitem Tracking Project Management Automated Build Test Management Analytics … Websites Virtual Machines Storage Databases Active Directory Networks …

11. Why Cloud? Quick to set up Scalable Easy to tear down No IT Pros involved Included in MSDN subscription Pay per use

12. CD for Farm/SB Solutions VSO QA DEV

13. CD FOR FARM/SB SOLUTIONS

19. Life as a SharePoint developer Daily tasks: Compiling your solutions/app (permanent) Testing your solution/app (permanent) Testing the deployment process (regularly) Reproduction of errors in closed environment (occasionally) Testing impact of Service Packs/Updates (occasionally) Functional testing (regularly) Performance testiong (regularly)

20. SharePoint Challenges Deployment/Testing requires „clean“ production like environment Deployment of SharePoint VMs time consuming, resource and performance hungry Multiple environments required (SP2010/2013, Service Packs) VMs have to be prepared for different versions of the own solution Deployment process complicated and error-prone

21. Goal Reduced effort for the developer Quicker development Continous testing of the deployment in complex environments (eg. multiple servers) Increased solution quality with regular testing

22. CD for Provider Hosted Apps VSO DEV SPO Dev site Azure Dev site SPO Prod site Azure Prod site

23. CD FOR PROVIDER HOSTED APPS

24. CD for Farm/SB Solutions VSO QA DEV

25. Release Management Server TFS QA DEV RM PROD

28. Summary Find problems earlier and save time & money VS Online + Azure = perfect for SharePoint CD Can be implemented in several steps Deployment of Farm Solutions with PowerShell Deployment of Apps with ootb VS Online It‘s worth it!

29. Resources SharePoint Solution Deployer spsd.codeplex.com spsd.codeplex.com SharePoint Code Analysis Framework spcaf.com spcaf.com SharePoint/TFS Continuous Integration Starter Pack (Chris O’Brien) matte.in/SharePointCI matte.in/SharePointCI Continuous Integration for SharePoint (MSDN) matte.in/CI4SharePointMSDN matte.in/CI4SharePointMSDN Configure a TFS Build Server for SharePoint Projects (MSDN) matte.in/TFSBuild4SP matte.in/TFSBuild4SP Deploying Provider Hosted SharePoint Apps to Azure (Kirk Evans) matte.in/CDSPApp2Azure matte.in/CDSPApp2Azure

30. Questions? matthias.einig@rencore.com @MATTEIN

31. Thank you!