[ALM Accelerator - QUESTION] Commit works on 1 dev env only and Test pipeline is not triggerd on an another env

[tocri]

What is your question?

I have a demo tenant and a customer tenant.

Since few months the ALM process was working fine on both environnements but someone has changed something on my projet and now my deployment is broken. he doesn't know what it made and i m trying to figure out what changes are made but i admit it, i m totally lost.

I have created my project on the client with the wizard. I have 6 environnements. DEV SQ,I Accept SQI, PRO SQI, DEV UA, ACC UA, PRD UA and a environment for ALM solution (ALM PROD)

First of all :

• If i click commit on a solution that is in DEV UA, the commit works.
• If i click commit on a solution that is DEV SQI, i have an error on the commit

Update Deployement settings, :

Error while retrieving queues. Queue not found: Azure Pipelines
'Azure Pipelines' queue Not Found. You will need to set the default queue manually. Please verify the permissions for the user executing this command include access to queues.

Invoke-RestMethod : {"$id":"1","innerException":null,"message":"TF215106: Access denied. Project Collection Build
Service (sqi-devsecops) needs Edit build pipeline permissions for build pipeline

So i follow this :

https://learn.microsoft.com/en-us/power-platform/guidance/alm-accelerator/setup-components-manually#set-permissions-for-the-project-build-service

except that i don't understand the step 7.

However, it doesn't change anything, I still get the same mistake.

Now,

After i commit a solution in the DEV UA environment, and if i click on deploy test. the pipeline is not trigering.

I don't the pipeline deploy-test :-(

Your help will be appreciate

thanks a lot

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20230906.1

AB#790

[mikefactorial]

@tocri there are two different permissions related issues here

'Azure Pipelines' queue Not Found. You will need to set the default queue manually. Please verify the permissions for the user executing this command include access to queues.

• You need to give permissions to the Project Build Service permission to the Build Queue described in Steps 9-11 in the document you referenced
  

Invoke-RestMethod : {"$id":"1","innerException":null,"message":"TF215106: Access denied. Project Collection Build
Service (sqi-devsecops) needs Edit build pipeline permissions for build pipeline

• You need to give permissions to the Project Build Service to create and edit pipelines described in Steps 7 in the document you referenced.
  
  

Make sure you are making these updates in the project specified in the deployment profile.

[mikefactorial]

Closing this out for now as there's no update in several weeks.

[CoEStarterKitBot]

@tocri This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.