Skip to content

Home

Jump to bottom
eugene van staden edited this page Jan 24, 2020 · 13 revisions

Getting started with our Power Platform DevOps tool

Provisioning Steps

Before you start ensure you have the following set up:

  1. You will also need to have an Azure DevOps organisation to use, if you don't have one, please create one at https://dev.azure.com
  2. You will need a Power Platform tenant, if you don't have one, please create one at https://powerapps.microsoft.com/

To kick start this process, just run the Provision.ps1 script

PS C:\dev> .\Provision.ps1

Which will start the process as below:

step1

The script will first install all the Pre-Requisites (git and Azure CLI) and once this is done you need to add the name of your Azure DevOps instance which will force you to log in.

Enter the name of your Azure DevOps Organization (https://dev.azure.com/<Name>):

login

After logging in and the script picks up your details you can select or create a new project. We will create a new one called demo1

Would you like to [C]reate a new Project or [S]elect and existing one (Default [S]): C

which is followed by:

Please enter the Name of the Project you wish to Create: demo1

Our project has been created in the Azure DevOps instance and the next step in the script will set the name of our new repo, which we will call demorepo

Enter the name for the Repository you wish to Create: demorepo

The script creates the new repo and clone the latest version of this template

project

repo

Now this is where things gets exciting. In the next step we will connect to our CDS/365 instance:

Press Enter to Connect to your CDS / D365 Tenant or [Q]uit:

login-d365

Once connected you need to select youe instance:

Select CRM Organization by index number:

And now you can select either an existing solution in this instance, or create a new one. We will now create a new one called Demo1

---- Please Select you Development Environment ------

dev-instance

Then select your staging environment:

---- Please Select your Deployment Staging (CI/CD) Environment ------

we are working on a feature will have the option to create a new instances for both a dev and the staging environments

  1. The new solution gets created in your dev environment
  2. This solution is extracted into your local source and a commit is made to your repo
  3. A default build definition gets created

build

  1. A default release definition gets created
  2. Library set per environment, Dev and Staging gets created

library

For more details check out Dylan Haskins where we will be documenting this approach in detail.

Part 1 : ALM Fundamentals and Maturity Part 2 : Solution Management, Versions and Source Control Part 3 : Data and Configuration Management Part 4 : Package Deployment Part 5 : Configuring Azure DevOps for Continuous Deployment Part 6 : PowerApps Portal Deployment Part 7 : Azure Companion Apps Part 8 : Solution Checker Integration Part 9 : Automated Testing of Code Part 10 : Automated Testing of UI

And listen to the chat between Eugene, Colin and Nick where they discuss building a set of ALM/DevOps tools for PowerApps Portals deployments

Tools used

  1. spkl task runner - just becasue its the best thing to have in a project
  2. XrmContext for earlybound -.net classes
  3. XrmDefinitelyTypes to generate TypeScript declaration files
  4. Microsoft.Xrm.DevOps.Data - generate filtered data compatible with the Configuration Data Migration Tool and perfect to automate your Power Apps Portals deployments
Clone this wiki locally