Ballzer0
commented
2 months ago I havent personally tested this, but i think you can do that by adding additional deployment steps in the administration app.
Open Srikanth-Singapuram opened 2 months ago
Ballzer0
commented
2 months ago I havent personally tested this, but i think you can do that by adding additional deployment steps in the administration app.
Srikanth-Singapuram
commented
2 months ago @Ballzer0 Thank you for your response. Indeed, I undertook the same actions manually. It would be beneficial to have the capability to incorporate additional environment deployments through the automatic creation of pull requests and the subsequent triggering of the pipeline upon the completion of the pull request in a below sequentional order.
Validation → Test → Integration → UAT → PROD
Is your feature request related to a problem? Please describe.
Currently, the ALM Accelerator provides support for three environments: Validation, Test, and Production (PROD). During the initial commit of the solution from "ALM Accelerator for Power Platform" app three pipelines corresponding to these environments will be established.
In addition, two new branches will be created: the 'feature' branch and the 'Solution' branch, which is named after the solution itself.
To incorporate additional environments, specifically Integration (INTG) and User Acceptance Testing (UAT), which are positioned between the Test and Production environments, it is necessary to create deployment profiles and steps, as well as to create the corresponding pipelines for the feature branch (yml: deploy-intg-SolutionName and deploy-uat-SolutionName).
When deploying the solution, one must select the Source Branch as the 'feature' branch and the 'Target Branch' as the 'solution' branch. This action will generate a pull request (PR), which will subsequently trigger the validation pipeline upon its creation.
Once the PR is completed and the feature branch is merged into the solution branch, the Test pipeline will be triggered.
To deploy the build to Production, it is essential to click on 'Deploy,' select the 'Source Branch' as the 'solution' branch, and the 'Target Branch' as 'Master.' This will create another pull request (PR). Following the approval of this PR, the 'deploy-prod-{solution_name}' pipeline will be initiated, facilitating the deployment of the solution to the production environment.
QUESTION / Feature :
Is there a method to trigger the INTG and UAT pipelines through pull requests and approvals? What would be the optimal approach to execute the deployment sequence: Validation → Test → INTG → UAT → PROD?
Describe the solution you'd like
Is there a method to trigger the INTG and UAT pipelines through pull requests and approvals? What would be the optimal approach to execute the deployment sequence: Validation → Test → INTG → UAT → PROD?
Describe alternatives you've considered
No response
Additional context?
No response