Zero To DevOps - Source Control and Release Strategy for Dynamics 365 Solutions - Crm Saturday 2017
Download as PPTX, PDF1 like1,360 views
The document discusses a DevOps strategy for Dynamics 365 solutions focusing on source control and release management. It emphasizes automation in maintaining release history, managing artifacts, and enabling continuous integration and deployment to enhance efficiency. The content also highlights the importance of team buy-in and best practices, underscoring the need for a structured approach to development and deployment processes.
![More information available at http://nullfactory.net
generator-nullfactory-xrm
[https://github.com/shanec-/generator-nullfactory-xrm]
http://nullfactory.net http://github.com/shanec-
Thank You
DesignedbyFreepikfromwww.flaticon.com
programmerbyChanutisIndustriesfromtheNounProject
designedbyfromFlaticon](https://image.slidesharecdn.com/zerotodevopssourcecontrolreleasestrategy-crmsaturday-public-170801125916/85/Zero-To-DevOps-Source-Control-and-Release-Strategy-for-Dynamics-365-Solutions-Crm-Saturday-2017-25-320.jpg)
Zero To DevOps - Source Control and Release Strategy for Dynamics 365 Solutions - Crm Saturday 2017
- 1. Zero to DevOps - Source Control and Release Strategy for Dynamics 365 Solutions Shane Carvalho Consultant | Dynamics 365 | Oakton
- 2. Hi! I’m Shane Carvalho • Geek. Developer. Blogger. • Mobile to multi-tenant SASS solutions in the .NET ecosystem. • Dynamics CRM 4 Dynamics 365. • Passion for ALM and DevOps. • Automate everything!!!
- 3. nullfactory.net github.com/shanec- @shanec_ Hi! I’m Shane Carvalho
- 6. But, wouldn’t it be nice to … • Automatically maintain a history of what went into a release? • What new features were included? • What bugs were fixed? • To have a single source of truth (not dependent on a CRM instance) • Rebuild your custom plugin/workflow assemblies – inject them into your CRM solution as part of a single build. • Rollback individual artifacts or commits. • Compare differences between releases. • Automate the entire deployment a CRM solution with the click of a button?
- 7. The Solution SolutionPackager.exe Official CRM SDK Individual Parts
- 8. The Solution SolutionPackager.exe Official CRM SDK Individual Parts
- 9. The Solution Project Structure SolutionPackager.exe Official CRM SDK Visual Studio Solution Official CRM SDK via NuGet Packages Helper Scripts (via Microsoft.Xrm.Data.PowerShell module)
- 10. Source Control – Build Definition The Solution Project Structure SolutionPackager.exe Official CRM SDK Visual Studio Solution Official CRM SDK via NuGet Packages Deployment – Release Definition Helper Scripts (via Microsoft.Xrm.Data.PowerShell module)
- 11. Source Control – Build Definition The Solution Project Structure SolutionPackager.exe Official CRM SDK Visual Studio Solution Official CRM SDK via NuGet Packages Deployment – Release Definition Scaffolding via Yeoman generator (generator-nullfactory-xrm) Helper Scripts (via Microsoft.Xrm.Data.PowerShell module)
- 12. Development Environment CRM Developer – Technical CRM Developer – Functional CRM Developer – Technical Build / Release Manager CI Build “Release” Build Deploy to UAT UAT Environment Pull Solution Typical Application Lifecycle Apply Versioning
- 13. The Challenge - Demo Development Environment UAT Environment VSTS using Git Team Build Release Management
- 14. Now, what does this mean?
- 15. No more “Golden” CRM Instance Deployment is not dependent on a source CRM Instance
- 16. A Single Source of Truth April 3.0x Release Bug Fix #10 Feature X Partial Feature X Done Sprint 4 QA Release Point in Time / Commits The Repository is the Source of Truth
- 17. A standard way of storing and managing projects across the organization. Project A & B Developer Project C Developer Project A Project B Project C Consistent way of Managing Projects
- 18. Traceability User Story / Feature Task Bug CommitAssociated with MS Build Commit Task Commit Task Commit Commit Commit Commit Build 1 Build 2 Build 3 Automatically maintain a history of what went into a release. Associated with Associated with Associated with
- 19. Quality of Artifacts – Integrity of Solution Ensure that your product can be built and deployed at any given time MS Build Continuous Integration / Scheduled (nightly) Build Commit Trigger 3AM Week Nights Continuous Deployment Release Success Success Automated
- 21. Form of Documentation VSTS Release Documentation Environment Specific Configuration Deployment Steps + Secure Configuration
- 22. Dynamics 365 Environment Visual Studio Team Services VSTS MS Build VSTS Release Repository Build + Test Release Bring Your Own Infrastructure
- 23. Deployment Guy Authorise Releases QA Release Approver UAT Release Manager or Approvers Group
- 24. Things to keep in mind… Dependence on the SDK tools Buy-In of the team Not a silver bullet You still have to follow the best practices when developing and deploying CRM Solutions. DevOps is people following a process enabled by products to deliver value to our end users. – Donovan Brown
- 25. More information available at http://nullfactory.net generator-nullfactory-xrm [https://github.com/shanec-/generator-nullfactory-xrm] http://nullfactory.net http://github.com/shanec- Thank You DesignedbyFreepikfromwww.flaticon.com programmerbyChanutisIndustriesfromtheNounProject designedbyfromFlaticon
- 26. Thank you
- 27. Step1 Visual Studio Solution Scripts + Toolset Generate scaffold Demo Recap – Scaffolding
- 28. Pull-CrmSolution.ps1 SolutionPackager.exe Plugins Project Workflows Project Web resources Project Development Environment Export Step2 Repository Visual Studio Solution Demo Recap – The Setup
- 29. Build SolutionPackager.exe Step3 Repackage Managed.zip Unmanaged.zip MS Build Step4 Testing Environment Deploy-CrmSolution.ps1 Release Management Demo Recap – Build and Release