Closed
Bug 1400853
Opened 8 years ago
Closed 8 years ago
push updated bugzilla.mozilla.org live
Categories
(bugzilla.mozilla.org :: Infrastructure, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dylan, Assigned: dylan)
References
()
Details
bug 1399508 : Pass along transaction id to BMO API calls for linking back to the exact change in the revision history
bug 1391702 : Replace Bugzilla::User::validate_password() with calls to Data::Password::passwdqc
bug 1364233 : Add setting to force a group to require MFA and restrict users in that group who have not enabled MFA
| Assignee | ||
Updated•8 years ago
|
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(dhouse)
Resolution: --- → FIXED
I updated bmo-nubis with the latest production code.
I've pushed it and that triggered the staging build and deploy:
https://sso.admin.us-west-2.bugzilla-aws.nubis.allizom.org/jenkins/job/bugzilla-build/72
However, it is still breaking on the new algoritm:bloomfilter package since that doesn't exist for in the aws/nubis env.
Dylan, you'd remarked that the aws bundle is not working. Could you point me to a log or something for that? Or is the vendor tarball building now? (if I wait long enough .. ;)
Flags: needinfo?(dhouse) → needinfo?(dylan)
The bundle is working now after the nubis upgrade last thursday. A push of the latest code to the bmo-nubis master branch triggered a stage build an deploy. Both were successful: https://sso.core.us-west-2.bugzilla-aws.nubis.allizom.org/jenkins/job/bugzilla-deployment/11/
Flags: needinfo?(dylan)
You need to log in
before you can comment on or make changes to this bug.
Description
•