Closed
Bug 1076888
Opened 10 years ago
Closed 10 years ago
please deploy fxa-oauth and fxa-content train-22 to production
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jrgm, Assigned: ckolos)
Details
(Whiteboard: [qa+])
Chris, Please build production stacks for fxa-oauth-server and fxa-profile-server with these paramenters: OAuth Server: AppVersion 0.22.0-1 ProvisioningVersion 20141001142205 Profile Server: AppVersion 0.22.0-1 ProvisioningVersion 20141001142205 RPMS: fxa-oauth-server-svcops-0.22.0-1.x86_64.rpm fxa-profile-server-svcops-0.22.0-1.x86_64.rpm Version check: $ curl https://oauth.stage.mozaws.net/; echo; curl https://profile.stage.mozaws.net/; echo; { "version": "0.22.0", "commit": "055174aa2925f6f61cfc16905f2a3a3949602781" } { "version": "0.22.0", "commit": "9f8fe75df765b8d9cb37211993018afa590ec0c8" }
Comment 2•10 years ago
|
||
Quick sanity check looks good. How does the flow usually work, :ckolos? You set RESOLVED FIXED, and then I set VERIFIED/FIXED?
Comment 3•10 years ago
|
||
There are some bobbles with the avatar stuff, so we'll come back to this tomorrow.
Flags: needinfo?(kthiessen)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•