dotnet
Operationalize weekly image update tasks
Goal
Motivation and Business Impact
Today, there is a fair amount of work that has to happen to keep the images used in dotnet-helix-machines both up-to-date and maintain the promises made such as keeping images updated and the regular tick-tock of Visual Studio version updates for the "current" version.
We would like to document this process and have it be handled by the new dncengopsvendors team. We have existing processes for the helix machines "end of life" policy and Artifact updating / end-of-life, this would represent an extension of these responsibilities.
Business Objectives
- [ ] P0: Visual Studio version update tick-tock and any new automation required is documented and run regularly by the vendor team
- [ ] P0: Azure Gallery base image update version work (and any new automation required) is documented and run regularly by the vendor team
- [ ] P1: Vendor team can generate rollout release notes for dotnet-helix-machines repo
- [ ] P1: Vendor team can generate rollout pull requests for dotnet-helix-machines repo
- [ ] P2: Automate generation of rollout notes for dotnet-helix-machines repo via custom commit messaging
One-pager
TODO
Timeline
| Week | Milestone | Status |
|---|---|---|
| 1 | Data gathering - inventory what is currently being done, by whom, and where docs for this live | Not Started |
| 2-3 | Implementation: Draft documents for process, share with vendor team | Not Started |
| 4 | Execution: Have vendor team run processes and adjust automation / docs to adjust | Not Started |
I just went through image update today and wrote this record of the steps I took. Hopefully it's a helpful starting point.
There are few other docs relevant to this:
Leaving this open until the vendor team successfully executes on rollout PR/release notes generation, but the work here is complete.
