If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Require user confirmation before running pushsnip

RESOLVED WONTFIX

Status

Release Engineering
Release Automation
P3
normal
RESOLVED WONTFIX
6 years ago
4 years ago

People

(Reporter: coop, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [release-process-improvement][automation][updates][simple])

(Reporter)

Description

6 years ago
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

4 years ago
Product: mozilla.org → Release Engineering
Found in triage.
Component: Other → Release Automation
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]
I doubt we'll get to this before Balrog is in production for releases.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.