Share
Report
83Hello everyone,
Please let me know if this is not the correct forum for this question.
We have started using the power platform build tools to help us create pipelines for Source Control use and we are creating one now that we want to extract the code from GIT, pack it up, and deploy it to our UAT environment.
I have been running through the PowerPlatform_DevOps_Module*.pdf's and my question is around importing the application to a UAT type environment.
According to the steps in this document and the statement.
"Your unmanaged solution is checked into source control, but you need to have a managed solution to deploy to other environments such as test and production. To obtain your managed solution, you should use a Just-In-Time (JIT) build environment where you would import your unmanaged solution files then export them as managed. These managed solution files will not be checked into source control but will be stored as a build artifact in your pipeline. This will make them available to be deployed in your release pipeline"
I need to create a pipeline to pack a solution, import that solution to my build server, then export that solution as a managed solution, and finally publish the artifact to a staging dir.
to start I think I'm confused as to why I have to connect back to DEV to export the solution, when it's already in GIT. I was thinking, why couldn't I clone it from GIT, pack it up, and push it to UAT? In short why all the extra steps? Has anyone else built something like this?
we haven't dove into what our branching strategy may look like, so I know that's a factor.
Details:
Environments:
DEV, UAT, PROD
Concept:
Build in DEV, trigger pipeline to load into GIT
Deploy to UAT, user acceptance testing begins
if issues are found, dev is notified and issues are fixed
run pipeline to load it into GIT
deploy to UAT, rinse and repeat
Once all testing is done.
run pipeline to deploy from GIT to PROD
All responses (
Answers (
