Closed mmitche closed 1 month ago
The rollout required a hotfix to unblock https://github.com/dotnet/arcade-services/pull/3723. This is because the previous Maestro version had a broken darc add-build-to-channel
command (which was the original reason for a rollout), so we had to pin darc to a previous working version
After this, we had some issues with publishing, but this was an arcade issue, which was fixed
After this the rollout succeeded without any issues
Purpose
This issue tracks the
arcade-services
repository rollout. On top of the Rollout instructions described on the wiki, it provides the person responsible for the rollout checklist of the steps that need to be performed to rollout services in this repository. All relevant information, including the rollout PR, issues encountered during the rollout and steps taken to resolve them should be linked or added to this issue to keep full audit trail of changes rolled out to production.Process
Build status check
Rollout
column in the Product Construction board - move any issues rolled-out last week intoDone
Rollout preparation
main
that you want to rolloutrollout/YYYY-MM-DD
from that commitrollout/YYYY-MM-DD
branch toproduction
[Rollout] Production rollout YYYY-MM-DD
production => main
PR inarcade-services
with the rollout merge commit (example). There should be no changes in the PR to any files. Do not merge the PR yet.Approval
phaseRollout
Approval
stage of the rollout build.production => main
PR inarcade-services
(⚠️ DO NOT SQUASH)Rollout
column of the Product Construction board intoDone
. Verify that PRs have a reference to the release at the bottom (example). If needed, manually add a comment with the reference (example)Rollout data
Rollout PRs
Rollout build
Rollout times
Use the following Kusto query to gather data about rollout times:
16:39
01:13
Useful links