You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
run the deployment using ALM acc. canavas app, after export to git has been successfully executed.
Deploy button runs the pipeline- deployToQA. Instead, it must run pipeline deployToUAT.
Anything else?
No response
AB#3269
The text was updated successfully, but these errors were encountered:
@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 iOS<https://aka.ms/o0ukef>
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
The text was updated successfully, but these errors were encountered: