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

push updated bugzilla.mozilla.org live

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Infrastructure
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: dkl, Assigned: fubar)

Tracking

Production

Details

(Reporter)

Description

3 years ago
can we please get a bmo production push.
revisions: ee940fd - 8d50642
bug 1118231 : Link to WebOps form missing from Infrastructure & Operations bug-entry form
bug 1118401 : Use https:// for linkification of CVEs and VCS-related output
bug 1077510 : Check a Vagrant/Docker project file (excl DB content) into the Bugzilla repo
bug 1089475 : Use "ThrowCodeError" when a database error occurs instead of dumping a stack trace
bug 1108685 : describecomponents.cgi?product=X shouldn't list default assignee if it's "nobody"
bug 1119114 : bzapi/configuration returns empty flag_types if no bug or attachment flag types are defined
bug 1118724 : Private comments on public bugs are sent unencrypted by email
bug 1119443 : Docker's generate_bmo_data.pl doesn't have similar bug status settings
bug 1119804 : Docker's generate_bmo_data.pl should add missing INCOMPLETE resolution
bug 1108805 : Creation of new data compliance bug
bug 1119977 : form.dev-engagement-event: Changes to default NEEDINFO
bug 1078099 : Clarify notes on createaccount.cgi
(Assignee)

Updated

3 years ago
Assignee: nobody → klibby
(Assignee)

Comment 1

3 years ago
Pushed to SCL3 and PHX1. New prod update script works as expected, though we did have a brief confusion on order of operations in regards to merging master to production.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(In reply to Kendall Libby [:fubar] from comment #1)
> Pushed to SCL3 and PHX1. New prod update script works as expected, though we
> did have a brief confusion on order of operations in regards to merging
> master to production.

i added a step to the bmo push mana page to catch this.
You need to log in before you can comment on or make changes to this bug.