Validating Azure Resource Templates within an Azure Build Pipeline
A key objective when it comes to implementing a Continuous Integration (CI) strategy is to ensure that there is no general degradation in the quality of code during a development cycle and in providing the earliest possible indication that a change in code has “broken the build”. Also, a lesser concern may be towards identifying the action or individual that has caused such a degradation. When…
Continue Reading The CRM Chap’s Article on their blog
Validating Azure Resource Templates within an Azure Build Pipeline
Blog Syndicated with The CRM Chap’s Permission
More About This Author
Array
- Dyn365CE29 August 2021Migrating Microsoft Dataverse Access Team Templates via Azure DevOps
- Dyn365CE22 August 2021Returning All Form Controls via JavaScript (Model-Driven Power App)
- Dyn365CE15 August 2021Exam PL-600 Revision Notes: Evaluating an Organisation, Metrics and Existing Systems
- Dyn365CE8 August 2021Exam PL-600 Revision Notes: Initiating Planning for your Power Platform Solution