Unanswered

Azure DevOps Pipeline\s - Power Platform Multiple Solutions

(0) Share

Report

Posted on by peterga80

Hi Power Platform community,

I have a usecase, where I will be deploying multiple Power Platform solutions using Azure DevOps. Each Power Platform solution contains different assets e.g. Tables, Plugins, Power Automate Flows etc.

What would be yours recommended approach regarding ALM for Power Platform:

1. Update only solutions that changed in specific time and have separate pipelines and handle dependencies

2. Have one atomic pipeline for everything and each time do upgrade of all solutions within the target environment

My preferred approach would be to use option 2, but in that case I would need to upgrade every solution each time that I will do a deployment, also with solutions that did not change.

Any other thoughts\ideas\experiences?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

thaman 2 on at

Like (0)

Report
Hey there,
I stumbled upon your post about deploying multiple Power Platform solutions with Azure DevOps and was curious about what route you ended up taking.
Since it's been a while, I'm really interested in hearing how things turned out:
Which strategy did you go for, and how's it working out?
Any bumps along the road or tips you've picked up?
Your journey could really help out folks here (myself included) facing similar dilemmas.
Cheers!

Was this reply helpful? Yes No
peterga80 2 on at

Like (0)

Report

So I have decided to have multiple separate solutions based on the functionallity (e.g. plugin, dataverse model etc) and our pipeline has multiple options defined, what solutions should be deployed to the production.
So we were able to define only solutions that has changes over the time so we were able to reduce the deployment and we were also able to handle the dependencies.

Was this reply helpful? Yes No
TK-22072225-0 9 on at

Like (0)

Report

has there been any updated on this?

Was this reply helpful? Yes No