Open nrawev opened 5 months ago
@nrawev Can you confirm if you have customized the deployment .yml pipelines on your end on top of the 'ALM Accelerator' build? The 'ALM Accelerator' follows the default branching strategy documented here which takes three environments into account (Validation, Test, Prod) and the deployment happens in the mentioned order.
Hi,
No we have not made any change to pipelines. We use standard offering for ALM accelerator.
Thanks, Nikunj
Sent from Outlook for iOShttps://aka.ms/o0ukef
From: Rajeev Pentyala @.> Sent: Thursday, June 6, 2024 2:33:23 PM To: microsoft/coe-starter-kit @.> Cc: Ranjan Nikunj @.>; Mention @.> Subject: Re: [microsoft/coe-starter-kit] [ALM Accelerator - BUG]: Pipeline does not run in correct sequence (Issue #8296)
@nrawevhttps://github.com/nrawev Can you confirm if you have customized the deployment .yml pipelines on your end on top of the 'ALM Accelerator' build? The 'ALM Accelerator' follows the default branching strategy documented herehttps://learn.microsoft.com/en-us/power-platform/guidance/alm-accelerator/branching-environment-strategy which takes three environments into account (Validation, Test, Prod) and the deployment happens in the mentioned order.
— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/coe-starter-kit/issues/8296#issuecomment-2152293649, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAIN33HWW5EZQYPZMIZ4Y5DZGBJJHAVCNFSM6AAAAABH4H5B76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSGI4TGNRUHE. You are receiving this because you were mentioned.Message ID: @.***>
@nrawev To understand the complete commit and deployment process to the target environment and how the branching works, please refer to the previous ticket
Describe the issue
We have are caught in an issue- when we deploy solution using ALM accelerator to downstream environmnets (UAT and QA), using ALM acclerator tool, the pipeline skips deployment to UAT and deploys code directly to QA. We can see in Azure DevOps Pipelines- deployToUAT never runs instead deployToQA always runs. Ideally deployToUAT pipeline must trigger first.
However when we go to devOps Pipeline- deployToUAT, and run it manually after changing the trigger to work branch, the pipeline runs fine.
It seems come config issue with ALM acc. that it skips UAT(validation environment) and run directly to QA(Test). Is this something you’ve come across.
Any help on the same would be highly appreciated.
Expected Behavior
Pipeline "deployToUAT" must run first and then pipeline "deployToQA" runs after.
What component are you experiencing the issue with?
ALM Accelerator Pipelines
What solution version are you using?
March release ALM accelerator
Steps To Reproduce
Anything else?
No response
AB#3269