[ALM Accelerator - QUESTION] How to force an update of deployment pipeline variables?

[sefa-phaag]

What is your question?

I have kind of a weird scenario. My company was purchased and so we have to move our ALM Accelerator / source code to the new tenant. I wanted to preserve my source code history (maybe a mistake, but we'll see), so I pushed the source code directly and created the various branches. I imported the unmanaged solution into my new development environment, created a solution profile, and committed the solution, but it didn't create the deployment pipelines, so I manually created them following the steps outlined here https://learn.microsoft.com/en-us/power-platform/guidance/alm-accelerator/setup-components-manually. However, there are dozens of pipeline parameters and I suppose I could create them manually, but is there some way to get the accelerator app to create them like it normally does?

At what point, exactly, is it supposed to update the pipeline parameters when you add new deployment settings configurations? Half the time, if I make changes to the deployment settings and then commit the solution, it ends with a warning that no changes were committed to source control.

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

November 2023

AB#1874

[RajeevPentyala]

@sefa-phaag The creation of 'pipelines' logic is in the 'Update Deployment Settings' task within the 'export-solution-to-git' pipeline. You can verify this by checking or sharing the log of the 'Update Deployment Settings' task to understand why the pipelines are not being created in your case.

Regarding your query about the warning "it ends with a warning that no changes were committed to source control", it's expected. Subsequent commits won't alter anything at the repo level, unless you add new components to the solution, but will update the deployment pipeline variables.

[sefa-phaag]

I did my best to go through the log and templates / PowerShell and from what I can tell, by the time it finally calls Set-BuildDefinitionVariables, the parameter $newBuildDefinitionVariables is null. There aren't any errors, but it also never outputs the Body or BuildDefinitionResourceUrl like it should otherwise.

I can't figure out why they should be null, though. I verified that it found the build definition and that the variables property is not null (it has the required EnvironmentName and ServiceConnection variables defined). As far as I can tell, there's no other place that is setting it null, so I'm kind of at a loss.

The full log is super long, but maybe it has something in it that I'm missing, but means something to you: raw log.txt

[RajeevPentyala]

@sefa-phaag We were unable to replicate this issue. Closing this issue for now. Kindly inform us if further assistance is required regarding this matter.

[sefa-phaag]

Forgot to update this thread (sorry), it appears that my issue came down to the fact that I hadn't updated the pipeline path in all the branches prior to committing the solution. I assumed (incorrectly) that checking in a change where I had updated the deploy-env-solution.yml files would flow through the process, but I had a lot more success updating those files during the initial source commit (e.g. from git; not from the ALM Accelerator). When I did that, it built out all the pipelines as soon as I committed my solution in the Accelerator.

[mikefactorial]

@sefa-phaag thanks for following up and for detailing the issue. Always helps to get closure and I'm sure will help others as well. Thanks again!