Closed
Bug 1053389
Opened 11 years ago
Closed 10 years ago
Please deploy Loop-Client 0.4.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: jbonacci, Unassigned)
References
Details
(Whiteboard: [qa+])
No description provided.
Reporter | ||
Updated•11 years ago
|
Whiteboard: [qa+]
James, please let me know if there's anything you need from me to qualify this before the push.
Reporter | ||
Comment 2•11 years ago
|
||
:ashughes unless you guys want to point your devices at Stage, I would say, check the specific 0.4.0 changes as soon as they go to Production. For the client side, Production is really "the place" for testing changes. (sounds contrary, I know).
I will be offline later, so whatever you and :jsmith normally do to test a new client...
Thanks James. For the Desktop Client, I will schedule a new round of smoketesting once this lands in production. For the Mobile side, I think TEF is handling that -- Jason, maybe you can coordinate?
Comment 4•11 years ago
|
||
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #3)
> Thanks James. For the Desktop Client, I will schedule a new round of
> smoketesting once this lands in production. For the Mobile side, I think TEF
> is handling that -- Jason, maybe you can coordinate?
Massimo would be the person to ask here from the TEF side.
Flags: needinfo?(mbarone976)
Comment 5•10 years ago
|
||
Now the staging bug is verified, when can we push this?
Reporter | ||
Comment 6•10 years ago
|
||
Yes, waiting for an OPs rep to take this and finish the work.
Comment 7•10 years ago
|
||
(In reply to James Bonacci [:jbonacci] from comment #6)
> Yes, waiting for an OPs rep to take this and finish the work.
Can we move this forward please?
Flags: needinfo?(bwong)
Updated•10 years ago
|
Assignee: nobody → dwilson
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(bwong)
Comment 8•10 years ago
|
||
This has been deployed to production. Please test at your convenience.
Assignee: dwilson → nobody
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•10 years ago
|
||
:jsmith
:ashughes
:standard8
The Loop-Client prod env is ready for verification.
Reporter | ||
Comment 10•10 years ago
|
||
OK. With OPs help verified the processes and apps running, verified the code.
Here is what I see from my end:
In the browser: https://call.mozilla.com
returns "Welcome to the Loop web client."
In the browser: https://call.mozilla.com/config.js
returns
var loop = loop || {};
loop.config = {serverUrl: 'https://loop.services.mozilla.com'};
We have our version string now in Prod:
In the browser: https://call.mozilla.com/VERSION.txt
returns
0.4.0
8a1240f0a0f8d85c77379dae0556feca71aa38d2 Wed, 13 Aug 2014 20:00:10 +0000
which matches what we get from 'rpm'
loop-client-svcops 0.4.0-3 x86_64 5543004
puppet-config-loop 20140729184904-1 x86_64 13881
(well, ok, 0.4.0 and 0.4.0-3)
to be expected
curl -I https://call.mozilla.com/
HTTP/1.1 200 OK
...etc...
In the absence of end-to-end (and a dead phone) that's as far as I can go.
Waiting on Loop-Client Dev/QA to finish the verification.
Comment 11•10 years ago
|
||
I gave this a quick end-to-end on desktop and it worked fine. Thanks.
Reporter | ||
Comment 12•10 years ago
|
||
Same here (my phone is borked).
Calling this one a win.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•