The arcade-services build is structured such that we deploy a new version of the darc tooling before we deploy the maestro application to the service fabric cluster. However, there's no direct dependency between these two jobs, so we run the risk of the maestro deployment finishes, signaling repos that a new version of darc is available, however the publishing pipeline may have not finished publishing the tool to the feed yet.
This exact situation happened on this rollout build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2041249&view=results
We should change the pipeline so that we only deploy the service once the publishing stage has completed.
Release Note Category
Release Note Description
Removed race condition between the publishing of darc and the deployment of Maestro.
The arcade-services build is structured such that we deploy a new version of the darc tooling before we deploy the maestro application to the service fabric cluster. However, there's no direct dependency between these two jobs, so we run the risk of the maestro deployment finishes, signaling repos that a new version of darc is available, however the publishing pipeline may have not finished publishing the tool to the feed yet.
This exact situation happened on this rollout build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2041249&view=results
We should change the pipeline so that we only deploy the service once the publishing stage has completed.
Release Note Category
Release Note Description
Removed race condition between the publishing of darc and the deployment of Maestro.