What you will build

In this tutorial, you will generate a set of files for a new project based on a standardised template that will:

• To create a source repository to store your development changes
• Create pipelines which builds, validates and deploys code to specified environments
• Can also generate additional files during the project lifecycle as the solution grows
• Create unmanaged solutions in Master environment
• Using the ADO generator to create the pipelines etc - inputs and outputs
• Setup branch policies and repo permissions

To achieve this, you'll use our tool, Project Generator.

Prerequisites

• NPM and Node JS
• VS Code
• Git
• An Azure DevOps project
• A Power Apps Development Environment
• A Power Apps CI Environment
• A Power Apps Test Environment

Positive : For setting up the Power Apps environments, follow this lab.

Before you can generate a new project, you need to install the generator globally on to your local machine.

Firstly, open up a Command Prompt or PowerShell.

Next, install yo, the generator engine, and @capgeminiuk/generator-powerapps-project, our project generator.

npm install --global yo @capgeminiuk/generator-powerapps-project

Stay in command prompt or PowerShell and navigate to the folder you want the generate the project within. For example:

cd C:/code
mkdir my-project
cd my-project

Next, run the base generator to build the file structure for our project by running.

yo @capgeminiuk/powerapps-project

It may take a few seconds for you to be prompted, but eventually you will be prompted for several inputs:

Open the generated project in either VS Code or the file explorer and take this opportunity to browse through the files seeing what was created and how the values you've entered have been passed into the naming of files and folders.

To open your project in VS Code from command prompt run code .

Now we are going to generate our solution structure by running:

yo @capgeminiuk/powerapps-project:solution

You will again be prompted for several inputs:

You will then be prompted to overwrite the following files:

• .vscode\tasks.json
• deploy\PkgFolder\ImportConfig.xml

Enter y and press Enter

Open the Maker portal and switch environments to the Master

Navigate to Solutions in the left-hand pane and select + New solution

Enter the following details:

Select Create

First, you need to create a Personal Access Token (PAT) so that the generator can talk to Azure DevOps on behalf of your account.

Open Azure DevOps, select User settings (user icon with a little cog) and select Personal access tokens

Select + New Token then enter the following values:

Positive : Important: Copy the token to notepad as you'll need this later.

Negative : If Package Name and Azure DevOps Project name are the same then the generator will fail. In this case, rename the pre-created repo in Azure Devops by:

1. Go to the Project Settings
2. Under Repos, select Repositories
3. For the repo with the same name, use the three dots to rename the repo to ‘[existing name]_old'

Now you are going to set up Azure DevOps by running yo @capgeminiuk/powerapps-project:azuredevops. You'll be prompted for the following inputs, after entering the value for each one, press Enter:

If the generation was successful, the output should look like this:

Setting up Azure DevOps...
Generating variable groups...
Creating Package - ALMLAB variable group...
Creating Integration Tests - ALMLAB variable group...
Creating Cake - ALMLAB variable group...
Generating repository...
Creating almlab repository...
Pushing initial commit to https://cap-alm-lab@dev.azure.com/cap-alm-lab/ALMLab/_git/almlab
Generating builds definitions...
Found 2 YAML builds.
Creating pipelines/azure-pipelines-dynamics-365-extract.yml build...
Creating pipelines/azure-pipelines.yml build...
Extension: PowerPlatform-BuildTools is already installed.
Extension: sarif-viewer-build-tab is already installed.
Generating service connections...
Generating release definition...
Creating ALMLAB release...
Finished setting up Azure DevOps.
Done.

Within Azure DevOps navigate to Project Settings then under Repos, select Repositories.

Now select your repository called the package name you gave and select the Policies tab. Under Branch Policy select master.

Turn on:

• Require a minimum number of reviewers
  Configure the settings as described below:

  Field	Value
  Minimum number of reviewers	2
  Allow requestors to approve their own changes	Unchecked
  Prohibit the most recent pusher from approving their own changes	Unchecked
  Allow completion even if some reviewers vote to wait or reject	Unchecked
  When new changes are pushed:	Reset all code reviewer votes

• Check for linked work items ensuring Required is selected.
• Turn on Check for comment resolutions ensuring Required is selected.
• Turn on Limit merge types ensuring only Squash merge is checked.

Select the + (Add new build policy) button associated with Build Validation

Input the following values:

Select Save