[ALM Accelerator - BUG]: ALM Accelerator issue is not pushing solution in downstream environments (Validation /UAT / Prod)

[jhasaroj]

Describe the issue

Facing Issue in ALM Accelerator : Commit Solution is pushing the solution ,as unpacked code base Azure DevOps git repo. (Pipeline invoked : "export_solution_to_git") Also Deploy Solution is creating a pull request for approval . (Pipeline invoked : None) But its not moving the managed solution into downstream environments. (Validation / UAT / Prod). Specifically no associated yml pipeline is called. Not sure what I am missing over here. Its not throwing any error(s) or exception message. Only yml pipeline called is "export_solution_to_git" . How to invoke other pipelines and associated variables and json files configuration for deploying solution to target environments. (Validation / UAT / Prod)

---

Please find below screen grab of stages of deployment.

Even after pull request approval and marking it as complete no Pipeline is triggered. Although I can see yml files being generated at both Branches (Solution and Feature). These files are empty. (Earlier version of ALM Accelerator Canvas App, YML files were generated but Pipelines were not created explicity though App) Could you please help be decipher this. Except "Deploy Sol" all actions "Commit" ,"Delete Sol" & "Import"... All are working fine.

Please help with below specific queries :-

1. Do we need to explicitly pass "AzDO template Pipeline value" in deployment profile?
2. Do we need to explicitly pass "Pipeline YML file name" in deployment profile?
3. Once YML files is created for Deployment from template into the Solutions branch of DevOps . Do we need to create pipeline from those existing yml file and pass these details in as mentioned in step 2 above?
4. How app picks the path of pipeline details, if above fields / values are not mandatory?
5. Can the configuration done without the Validation environment. As initial starting point for most of the Power Platform application will be Development Environment. (We just want to move the code from Development --> DevOps--> UAT -->Prod ).
6. Is there any way via app (ALM Accelerator Canvas App) where by we can move solution though environment instead of selection of Branch. As We can see that option in the app. But can't make it work. Lastly but not the least,
7. If pull request is created between src: & target: . I am approving using same login id, will that trigger pipeline (or else with admin account and similar user account with same /similar email id). Thanks a lot for patience and support! Hope to hear from you.

Expected Behavior

Commit Solution / Deploy Solution shall call specific pipelines based on template to deploy Power Apps / Flow based solution into downstream environments. Not sure which specific steps needs to be configured. Also is it for solution specific or generic for all solutions.

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20240104.1

Steps To Reproduce

1. Accelerator Version: 1.0.20240104.1 (Managed)
2. Create a simple sample solution in power apps / power automate .
3. Set up ALM accelerator using ALM accelerator Power Platform Admin .
4. Configure User settings and User Profile. Setup Validations and UAT and Prod environment details.

Anything else?

AB#2087

[RajeevPentyala]

@jhasaroj I noticed that the 'Validation' deployment step was missing from your 'Deployment Profile' screenshot. Was that intentional?

Regarding your question about deployment .yml files, please be aware that when you commit the solution for the first time, a set of pipelines is automatically created under Pipelines -> All -> {RepoName - SolutionName} as shown below. Can you confirm if the pipelines were created in your case?

[jhasaroj]

Hi Rajeev, Thanks for reverting back.

Yes validation environment being missed was intentional, we are doing small poc with ALM Accelerator for our usages for ALM. Mostly in near future we will be sticking with this pattern due to single member team working on a solution.

With current ALM Accelerator canvas Version: 1.0.20240104.1. Its has created environment specific YML files & pipelines, under path {RepoName - SolutionName} for one solution. but these YML files are empty/blank. PFA image below.

Is there any specific parameter I am missing.

For another solution there was no such YML file and pipelines being created. Will check with few more testing and provide further details with screen shots.

[jhasaroj]

[jhasaroj]

Hi @RajeevPentyala , Is there way to raise Microsoft Ticket (Support or Advisory) to get this sorted in the client environment. Else, will it be feasible to assign any engineer from the CAT-team to triage this.

Hope to hear from you.

Thanks and regards, Saroj Kumar

[RajeevPentyala]

@jhasaroj Please mail me at rajeevpe(at)microsoft(dot)com with the details.

[Sinder88]

Any resolution to this? I seem to have a similar problem

[tocri]

Do you rename your deployment step name ? For exemple i have renamed Test to acceptation and when i wanted to deploy in acceptation, i was facing issue in devops:

To resolve this, i have just renamed my deployment step name to the original name as Test.

I don't know if it helps