-
Notifications
You must be signed in to change notification settings - Fork 78
Closed
Labels
Description
Purpose
This issue tracks the arcade-services repository rollout. 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 a full audit trail of changes rolled out to production.
Process
Build status check
- Check the status of the dotnet-arcade-services-daily pipeline
- Check the status of the arcade-services-official pipeline.
Rollout preparation
- Assign this issue to the FR area and to the current sprint.
- Create the rollout PR:
- Find a commit on
mainthat you want to rollout - Create a branch named
rollout/YYYY-MM-DDfrom that commit - Create a PR on GitHub from the
rollout/YYYY-MM-DDbranch toproduction - Name the PR
[Rollout] Production rollout YYYY-MM-DD - Link this issue in the PR description
- Find a commit on
- Merge (
⚠️ DO NOT SQUASH) the prepared rollout PR - Verify that a
production => mainPR was opened inarcade-serviceswith the rollout merge commit (example). There should be no changes in the PR to any files. Do not merge the PR yet. - Ensure the build is green and stops at the
Approvalphase
Rollout
- Approve the
Approvalstage of the rollout build. - Monitor the rollout build for failures.
- Note: this PCS exceptions query might help in diagnosing issues.
- Keep track of any issues encountered during the rollout either in this issue (or in a dedicated issue linked to this one)
- Merge (
⚠️ DO NOT SQUASH) theproduction => mainPR inarcade-services - Close this issue with closing comment describing a high-level summary of issues encountered during the rollout
- In case of rollback, uncomment the Rollback section below and follow the steps there