Multiple CI/CD Builds publishing the same app at the same time

[Mkublbock]

We have setup CD for one of our environments. Now, when we have multiple CI/CD builds running at the same time we run into this error:

Deployment failed. Errors: App ID : 6c4e6eb5-a230-492c-816b-31080263bfbf Message : { Deploying extension could not be started as there is another operation running on this environment. Please try again later or if the issue persists, please contact Microsoft Support and provide the Operation ID with the request. } - Job Id : 9e94763a-5aa9-4187-8e55-d72a3fa12e5f

Obviously this is because the builds are trying to publish the same app with different versions at the same time which doesn't work. However, because of this we do not always have the latest version published. Is there any way to wait until all previous deployments are successful and then start deployment or any other way around this?

[aholstrup1]

AL-Go has some support for controlling the concurrency of workflows using the workflowConcurrency setting. Maybe that would work for this case

https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md#workflow-specific-settings

[Mkublbock]

Thank you, we will take a look at it when we have time 👍🏻

[Mkublbock]

@aholstrup1 It's been quite some time but I just wanted to let you know that we have added the conditional setting

"workflows": ["CI/CD"],
"settings": {
  "workflowConcurrency": [ 
   "group: ${{ github.workflow }}-${{ github.ref }}",
   "cancel-in-progress: true"
  ]
}

and this now works really well, thanks!