Skip to main content

Microsoft Power Platform Build Tools for Azure DevOps Part 2

 

Microsoft Power Platform Build Tools for Azure DevOps Part 2

Create a Release to Import your solution to various environments

This is part II of Microsoft Power Platform Build Tool for Azure DevOps, in this article we are going to focus on how to create a release to deploy our solutions stored in our repository to various environments.


Create a new release




Click “Empty Job”





Name your Stage “Deploy To Test”

you can name your stage anything it suits you, based on your naming standards

Here you have to assign the Stage Owner as well.



In the following steps we are going to define:

  1. Artifacts, in our case is going to be our Git environment where we are storing our unpacked solution

  2. Stages, deployment to various environments we can create subsequent stages if one follows the other

    1. Pre-deployment conditions

    2. Post-deployment conditions

Artifacts



  1. Project:- Select your Project

  2. Source(repository):- your repository

  3. Default branch:- your branch

  4. Default version:- latest from the default branch


Add Job to Stage




Click on Deploy to Test and create the following





  1. PowerShell to read Solution Name

  2. Install “Power Platform Tools Installer”

  3. Power Platform Pack Solution

  4. Power Platform Import Solution


This Portion is pretty much straight forward we have defined these steps in Part 1

Labels:

Comments

Post a Comment

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.
Post a Comment
Read more

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...
5 comments
Read more

XMLHttpRequest vs Xrm.WebApi

  XMLHttpRequest vs Xrm.WebApi If you have written JavaScript code for Dynamics 365 you have seen the use of XMLHttpRequest or Xrm.WebApi to make server-side calls. The question is which one is the right one to use? So, let’s analyze the two types of calls. XMLHtttpRequest 1.        Synchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", false ); 2.        Asynchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", true ); So, passing true parameter is going to make asynchronous call while passing it false is going to make a Synchronous call. Xrm.WebApi 1.        Asynchronous a.        There is...
4 comments
Read more