It would be nice to have concrete data about SWAT windows without having to dig in the SAL. Some nice-to-have info: number of syncs per SWAT window and time spent deploying patches for a given SWAT window.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T193311 Track scap syncs that are part of a given SWAT window | |||
| Declined | • mmodell | T196411 Document scap swat command |
Event Timeline
Comment Actions
We looked into this at the RelEng offsite a bit. There are a few options here:
- We could require deployers to start, e.g., scap swat start before they are allowed to sync
- We add a --type argument that accepts some enum (e.g., deploy, swat) to each sync command that, if not provided, provides a prompt: Is this sync part of a SWAT? [y/N]
These both risk inconveniencing deployers with little benefit. We could mitigate this inconvenience somewhat by parsing the SAL message for messages matching ^SWAT: and not prompting in that case. The final thing we discussed was documenting the existing scap swat command that @mmodell worked on.
Comment Actions
Declining this in favor of T279322: Design m8s deployment workflows and tooling -- which encapsulates pipeline work as well.