Open Bug 1072113 Opened 11 years ago Updated 7 months ago

ship-it doesn't display the "do eet" time

Categories

(Release Engineering :: Applications: Shipit, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: hwine, Unassigned)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3371] )

There is no apparent way to order display of running jobs by time approved ("do eet" button pressed). Somewhat corner use case: when many releases are submitted in advance, but are approved slowly (e.g. to ensure delivery order or avoid tagging contention) it's not easy to spot "the last 2". While the "submitted" time is useful for tracking purposes, the "approval" time is more reflective of overall end-to-end time, as that's the last manual operation. So, it may be reasonable to switch which column is displayed. (The submitted time would still be available in the expanded record, just not immediately viewable.)
There's a ReleaseEvents table now that tracks all of the buildbot builders. It's generic though, and can track things that aren't buildbot jobs. It shouldn't be too difficult to have ship it update this table. However, I'm not sure "approval" time (the point at which "do it" is hit) is what you want, because that doesn't always mean "release is starting" - there could be release runner failures that prevent that. I don't have a strong opinion about this, I just want to make sure it's considered.
I'd be fine with either date, as long as we have it documented :) This is a corner case, and either date would improve that situation. Easiest implementation wins in my book.
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3364]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3364] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3369]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3369] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3371]
Mass component change for ship it bugs.
Component: Tools → Ship It
Priority: -- → P3
Component: Applications: ShipIt (backend) → Applications: ShipIt
Severity: normal → S3
QA Contact: hwine
You need to log in before you can comment on or make changes to this bug.