Closed
Bug 1077061
Opened 10 years ago
Closed 10 years ago
Please deploy Loop-Client 0.7.0 code to production
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Unassigned)
References
Details
We'd like to deploy the loop-client 0.7.0 release to production. https://github.com/mozilla/loop-client/releases/tag/0.7.0 This can be deployed after the stage bug is verified. CONFIG CHANGES: config/config.js needs some additional variables, the variables are: -- loop.config.fxosApp -- loop.config.fxosApp.name -- loop.config.fxosApp.manifestUrl I do not yet know the values of these. :ferjm please can you advise what these should be for our *production* environment (these can be updated later if necessary).
Flags: needinfo?(ferjmoreno)
Comment 1•10 years ago
|
||
The manifest URL is only available after uploading the app to the Market Place, and we are blocked as the MP team has not advised us about how to publish the app in a restricted mode.
Updated•10 years ago
|
Flags: needinfo?(ferjmoreno)
Reporter | ||
Comment 2•10 years ago
|
||
From the discussion on bug 1077059, no config changes are needed at this time.
Comment 3•10 years ago
|
||
This has been deployed to production with no config changes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 4•10 years ago
|
||
SUMMARY Spoke with deanw and bobm today regarding a prod re-spin to accomodate some ops changes necessary for addressing: 'Bug 1081086 - make hello.firefox.com point to the loop standalone client' (needed by Monday). PROD UPDATE 1. New stage deployment - Ops deployed an additional stage instance of loop-client 0.7.0 to be able to safely test cutover - Quick validation of new instance 2. Prod deployment - Ops deployed new instance to prod (one for 'call.mozilla.com', one for 'hello.firefox.com') to allow for testing - Ops applied DNS cutover - verified deployment with calls between Nightly and Aurora: a. using generated 'call.mozilla.com' domain b. substituting the generated domain 'call.mozilla.com' with new 'hello.firefox.com.' - Ops pointed both domains to single prod instance to complete deployment - re-verified loop-client works using either old/new domain Checking with ahughes to see if he wants to do any final checking, otherwise looks fine on our end.
Flags: needinfo?(anthony.s.hughes)
Looks like you have the bases pretty well covered. Thanks.
Flags: needinfo?(anthony.s.hughes)
You need to log in
before you can comment on or make changes to this bug.
Description
•