In this video, we explore CI/CD (continuous integration/continuous deployment) using Azure DevOps Pipelines to take our solution contents from version control (Git), package it up and deploy it to a Dynamics 365 Customer Engagement & Power Platform CDS instance. We also look at how we can recall a solution from any point in time as the basis for our deployment.

To make things easier for you, below are the strings used to specify the source folder and

Source Folder of Solution to Pack:
$(System.DefaultWorkingDirectory)/Azure_Source/D365_Solutions/$(SolutionName)

Solution Output File  and  Solution Input File:
$(System.DefaultWorkingDirectory)\$(SolutionName).zip

Your support by SUBSCRIBING to my YouTube channel is very much appreciated.

In this video, we explore CI/CD (continuous integration/continuous deployment) using Azure DevOps Pipelines to copy our Dynamics 365 Customer Engagement & Power Platform solutions to version control (Git) so that we can a) see what has changed over time and b) recall a solution at any point in time that was captured.

In the video, a couple of copy/paste blocks were used. I’ve provided them below for easy reference.

Powershell Script:

$date=$(Get-Date -Format 'yyyyMMdd')
Write-Host "##vso[task.setvariable variable=CurrentDate]$date"
Write-Host "Set CurrentDate to $date"

Command Line:

echo Commiting all changes
git config user.email "justin@notjust365.com"
git config user.name "Automatic Build"
git checkout master
git add --all
git commit -m "Automatic solution commit $(CurrentDate)"

echo Push code to repository
git -c http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)" push origin master

Your support by SUBSCRIBING to my YouTube channel is very much appreciated.

In this video, we explore CI/CD (continuous integration/continuous deployment) using Azure DevOps Pipelines to automate releasing Dynamics 365 Customer Engagement & Power Platform solutions between environments.

Your support by SUBSCRIBING to my YouTube channel is very much appreciated.