Closed
Bug 720851
Opened 12 years ago
Closed 11 years ago
Require user confirmation before running pushsnip
Categories
(Release Engineering :: Release Automation: Other, defect, P3)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: coop, Unassigned)
Details
(Whiteboard: [release-process-improvement][automation][updates][simple])
Almost reopened bug 508417 to cover this, but I think this is subtly different. For 10.0b5, I was in a rush and cut-n-pasted the pushsnip command from the release notes when I meant to run backupsnip. pushsnip should guard against this by requiring an additional user confirmation before proceeding. We should of course allow for a flag to override the confirmation when being run from automation.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 2•11 years ago
|
||
We can add -f parameter to suppress user confirmation to be used by automation.
Whiteboard: [release-process-improvement][automation][updates] → [release-process-improvement][automation][updates][simple]
Comment 3•11 years ago
|
||
I doubt we'll get to this before Balrog is in production for releases.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•