Closed Bug 1379170 Opened 8 years ago Closed 7 years ago

publish e-mails to release-drivers are LIES when scheduling changes in Balrog

Categories

(Release Engineering :: Release Automation, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: garbas)

References

Details

(Whiteboard: [releaseduty])

We added support for this as part of the multiple signoff project (specifically, in https://bugzilla.mozilla.org/show_bug.cgi?id=1347212), but forgot to update the e-mail templates for this new case. We should update them to stop saying things like "updates are live" and instead say things like "updates will be published at time X".
Assignee: nobody → mtabara
Since we turned on signoffs, we no longer have anything in the existing graph saying the change took place or not in terms of publishing to Balrog. Because of that, we cam: 0. Short-time today solution is to at a bare minimum change these emails to state that the changes are "scheduled" instead of "updated". 1. Mid-term solution is to add some external/internal logic that polls Balrog and chains the email notification status to that. 2. Correct long term solution will be Ship-it V2 which will solve this problem as the signoffs will be in the graph.
Assignee: mtabara → rgarbas
We need to fix this ASAP. It's the third beta in a row with bogus emails. I'll bump this in our priority.
Priority: -- → P1
Whiteboard: [releaseduty]
See Also: → 1386319
Severity: normal → critical
Status: NEW → ASSIGNED
See Also: → 1388932
PR landed and fixed the issue. I think we can close this. Thanks :garbas for the help with this!
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.