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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/rollout-issue.md
+4-28Lines changed: 4 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,8 @@ This issue tracks the `arcade-services` repository rollout. It provides the pers
15
15
16
16
## Build status check
17
17
-[ ] Check the status of the [dotnet-arcade-services-weekly](https://dev.azure.com/dnceng/internal/_build?definitionId=993) pipeline
18
-
-[ ] Rotate any secrets that need manual rotation
19
-
-[ ] Check the status of the [arcade-services-internal-ci](https://dev.azure.com/dnceng/internal/_build?definitionId=252) pipeline. Try to fix issues, if any, so that we have a green build before the rollout day.
20
-
-[ ] Check the `Rollout` column in the [Product Construction](https://github.com/orgs/dotnet/projects/276) board - move any issues rolled-out last week into `Done`
18
+
-[ ] Check the status of the [arcade-services-internal-ci](https://dev.azure.com/dnceng/internal/_build?definitionId=252) pipeline.
19
+
-[ ] Check the `Rollout` column in the [Product Construction](https://github.com/orgs/dotnet/projects/276) board - move any issues rolled-out **last week** into `Done`
21
20
22
21
## Rollout preparation
23
22
-[ ] Create the rollout PR:
@@ -26,18 +25,15 @@ This issue tracks the `arcade-services` repository rollout. It provides the pers
26
25
- Create a PR on GitHub from the `rollout/YYYY-MM-DD` branch to `production`
27
26
- Name the PR `[Rollout] Production rollout YYYY-MM-DD`
28
27
- Link this issue in the PR description
29
-
-[ ] Link the rollout PR to the [Rollout PRs](#rollout-prs) section of this issue
30
28
-[ ] Merge the prepared rollout PR (⚠️ **DO NOT SQUASH**)
31
-
-[ ] Link the rollout build to the [Rollout build](#rollout-build) section of this issue
32
-
-[ ] Verify that Maestro opened a `production => main` PR in `arcade-services` with the rollout merge commit ([example](https://github.com/dotnet/arcade-services/pull/2741)). There should be no changes in the PR to any files. **Do not merge the PR yet**.
29
+
-[ ] Verify that a `production => main` PR was opened in `arcade-services` with the rollout merge commit ([example](https://github.com/dotnet/arcade-services/pull/2741)). There should be no changes in the PR to any files. **Do not merge the PR yet**.
33
30
-[ ] Ensure the build is green and stops at the `Approval` phase
34
31
35
32
## Rollout
36
33
-[ ] Approve the `Approval` stage of the rollout build.
37
34
-[ ] Monitor the rollout build for failures.
38
35
- Note: this [PCS exceptions query](https://ms.portal.azure.com#@72f988bf-86f1-41af-91ab-2d7cd011db47/blade/Microsoft_OperationsManagementSuite_Workspace/Logs.ReactView/resourceId/%2Fsubscriptions%2Ffbd6122a-9ad3-42e4-976e-bccb82486856%2FresourceGroups%2Fproduct-construction-service%2Fproviders%2Fmicrosoft.insights%2Fcomponents%2Fproduct-construction-service-ai-prod/source/LogsBlade.AnalyticsShareLinkToQuery/q/H4sIAAAAAAAAAz2MOw6DMBBE%252B5xiSlsiRZDS5i7GjGQXu0brRSSIwyekoH4fvjMXr0377cBWaIRXYfckC17QtoV4H%252Bcf7KtIsroTua3qIWL6YKoaLn%252FA4ylxgNBLOxOjzrT%252FMJdk%252FgV08ryabQAAAA%253D%253D) might help in diagnosing issues.
39
36
-[ ] Keep track of any issues encountered during the rollout either directly in this issue, or in a dedicated issue linked to this issue
40
-
-[ ] When finished, update the rollout stats in the [Stats](#stats) section below. The statistics will be available in Kusto a few minutes after the build was finished
41
37
-[ ] Merge the `production => main` PR in `arcade-services` (⚠️ **DO NOT SQUASH**)
42
38
-[ ] Move rolled-out issues/PRs in the `Rollout` column of the [Product Construction](https://github.com/orgs/dotnet/projects/276) board into `Done`. Verify that PRs have a reference to the release at the bottom ([example](https://github.com/dotnet/arcade-services/pull/3663)). If needed, manually add a comment with the reference ([example](https://github.com/dotnet/arcade-services/pull/3680#issuecomment-2191186247))
43
39
-[ ] Close this issue with closing comment describing a high-level summary of issues encountered during the rollout
@@ -46,36 +42,16 @@ This issue tracks the `arcade-services` repository rollout. It provides the pers
46
42
<!-- UNCOMMENT HERE IN CASE OF A ROLLBACK
47
43
## Rollback
48
44
49
-
In case the services don't work as expected after the rollout, it's necessary to roll back.
45
+
A rollback was necessary during this rollout.
50
46
51
47
- [ ] Announce the issues on the [Rollout channel](https://teams.microsoft.com/l/channel/19%3a72e283b51f9e4567ba24a35328562df4%40thread.skype/Rollout?groupId=147df318-61de-4f04-8f7b-ecd328c256bb&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47), rollout issue in [AzDO](https://dev.azure.com/dnceng/internal/_workitems/)
52
48
- [ ] Notify the partners that we'll be rolling back
53
49
- [ ] Rollback as described on the [Rollback / Hotfix](https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng%20Services%20Wiki/831/Rollout?anchor=rollback-/-hotfix) wiki page
54
50
- [ ] Validate the rolled-back services are running as expected
55
51
- [ ] Announce successful rollout on the [Rollout channel](https://teams.microsoft.com/l/channel/19%3a72e283b51f9e4567ba24a35328562df4%40thread.skype/Rollout?groupId=147df318-61de-4f04-8f7b-ecd328c256bb&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47)
56
52
- [ ] Notify the partners that the rollback has been finished (as reply on the original email)
57
-
58
-
### Rollback PRs
59
-
- `<TO BE FILLED (IF APPICABLE)>`
60
53
-->
61
54
62
-
# Rollout data
63
-
64
-
## Rollout PRs
65
-
66
-
* The main PR: <TOBEFILLED>
67
-
68
-
## Rollout build
69
-
70
-
* Rollout AzDO build: <TOBEFILLED>
71
-
72
-
## Rollout times
73
-
74
-
Use the following [Kusto query](https://dataexplorer.azure.com/clusters/engsrvprod/databases/engineeringdata?query=H4sIAAAAAAAAA52QP0%2FDQAzF934KK0tzUlgYU2UAtUJdUNWyIRSZxG0O3eWCzwHKn%2B%2BOE4oIjNxkvbN%2Fz341VQ6Z4LEnPpYdMnoS4phug3Ohl3WdgwvtAQqzmDkSuCJZ9oxiQwsFpKU9NWRQ7i1H2QkeKIcobEfR4R%2FNwNsM9N1YT862tKUqcB1H7R2eG9JtLnvr6nUNRQFq8OvrWhcE26YTt6mLOTXH3ntk%2B0rqiiy6qteh3VAPxiYDautBxZeJehruODxQJTA5dB%2FYo5SiXbHDNh2mz77YGSRNk3ufaEIfi1mnR8oIup1vmC46pT2hg3RsMvM7pUmIFWru6STNn8QVOAaQaLHp752NDfRRo4MlcpUYk33jQ5T%2F8ZfUuXAcDFbnKxCKEpW7%2BATR1TCdDgIAAA%3D%3D) to gather data about rollout times:
0 commit comments