Page MenuHomePhabricator

Track scap syncs that are part of a given SWAT window
Open, NormalPublic

Description

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.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 27 2018, 11:48 PM
thcipriani triaged this task as Normal priority.Jun 4 2018, 9:23 PM

We looked into this at the RelEng offsite a bit. There are a few options here:

  1. We could require deployers to start, e.g., scap swat start before they are allowed to sync
  2. 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.

Vvjjkkii renamed this task from Track scap syncs that are part of a given SWAT window to k1daaaaaaa.Jul 1 2018, 1:14 AM
Vvjjkkii raised the priority of this task from Normal to High.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
Samwilson renamed this task from k1daaaaaaa to Track scap syncs that are part of a given SWAT window .Jul 1 2018, 4:56 AM
Samwilson lowered the priority of this task from High to Normal.
Samwilson updated the task description. (Show Details)
Samwilson added a subscriber: Aklapper.
thcipriani moved this task from Needs triage to Debt on the Scap board.Jul 11 2018, 12:22 AM
mmodell changed the status of subtask T196411: Document scap swat command from Open to Stalled.Feb 25 2019, 5:46 PM