Closed
Bug 1261815
Opened 10 years ago
Closed 10 years ago
Please deploy loop standalone 1.2.5 to STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Assigned: dmaher)
Details
------------------
RELEASE NOTES
------------------
https://github.com/mozilla/loop/blob/v1.2.5/CHANGELOG.md
COMPARISONS
https://github.com/mozilla/loop/compare/v1.1.10...v1.2.5
TAGS
https://github.com/mozilla/loop/releases/tag/v1.2.5
https://github.com/mozilla/loop/commit/fa65cf27960fa6cfac7327a210ea1482f7b609c7
Timescales: We'd like this to be deployed to production this week please, assuming no issues found.
Comment 1•10 years ago
|
||
==========
PRE-DEPLOYMENT
==========
Current version on staging of loop server is 0.20.1
With loop.server values set to https://loop.stage.mozaws.net/v0
end-2-end test calls (shared URL) - OK
Video/audio mute/unmute - OK
messaging - OK
Tab & window-sharing - OK
privacy & ToS links - OK
Feedback screens - OK
push notifications - OK
URL checks all pass using the following expected values:
location = https://www.mozilla.org/firefox/hello/
root = https://call.stage.mozaws.net
loop_server = https://loop.stage.mozaws.net
loop_server_version = 0.20.1
loop_server_push_server_config = https://loop.stage.mozaws.net/push-server-config
loop_server_push_server_uri = wss://autopush.stage.mozaws.net
loop_fxos_app_name = Hello Stage
feedbackProductName = Loop
privacyWebsiteUrl = https://www.mozilla.org/privacy/firefox-hello/
legalWebsiteUrl = https://www.mozilla.org/about/legal/terms/firefox-hello/
roomsSupportUrl = https://support.mozilla.org/kb/group-conversations-firefox-hello-webrtc
guestSupportUrl = https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode
unsupportedPlatformUrl = https://support.mozilla.org/kb/which-browsers-will-work-firefox-hello-video-chat
learnMoreUrl = https://www.mozilla.org/hello/
homePage = https://github.com/mozilla-services/loop-server/
fakeTokBox = False
fxaOAuth = True
name = mozilla-loop-server
version = 0.20.1
----------
deployment_tests/test_deployment.py::test_header PASSED
deployment_tests/test_deployment.py::test_server_config PASSED
deployment_tests/test_deployment.py::test_server_response PASSED
deployment_tests/test_deployment.py::test_push_server_config PASSED
----------
| Reporter | ||
Comment 2•10 years ago
|
||
For QA:
In lieu of the version.txt file, the most obvious changes are:
- "Join the conversation" now has text around it, e.g. "Surfing together is just way more fun!"
- User's local & remote video are now shown near the top-right.
- Other improved views in the middle of the display
- When two-way communication is established, clicking on the items being shared should display a click indication on the peer's display.
Also, we now have limited functional tests:
https://github.com/mozilla/loop/blob/v1.2.5/docs/Developing.md#functional-tests
Summary - check out the repo at `v1.2.5`, make install, make build. For testing staging you should be able to do:
TEST_SERVER=stage TEST_BROWSER=nightly USE_LOCAL_STANDALONE=0 make functional
for prod:
TEST_SERVER=prod TEST_BROWSER=nightly USE_LOCAL_STANDALONE=0 make functional
The functional tests currently only test a single browser instance talking to itself. They create a conversation, open the standalone, join on both sides, check that remote video is received and then end the call.
We should still be testing with cross browser, e.g. using Google Chrome for the standalone talking to nightly + release.
However, the functional tests should give confidence that the standalone is working reasonably well.
| Assignee | ||
Comment 3•10 years ago
|
||
As per chartjes' request:
region: eu-west-1
id: i-25489fa9
tags["Type"]: loop_client
tags["AppGitRef"]: refs/tags/v1.2.5
tags["Stack"]: loopclientstage1-loop-client-app-58
public_dns_name: ec2-54-171-146-248.eu-west-1.compute.amazonaws.com
launch_time: April 4, 2016 at 4:05:12 PM UTC+2
| Assignee | ||
Comment 4•10 years ago
|
||
The information in comment #3 is outdated (that node/ELB combo never became healthy and was killed off by the ASG). Instead:
region: eu-west-1
id: i-7a3647f2
tags["Type"]: loop_client
tags["AppGitRef"]: refs/tags/v1.2.5
tags["Stack"]: loopclientstage1-loop-client-app-58
public_dns_name: ec2-54-194-178-26.eu-west-1.compute.amazonaws.com
launch_time: April 4, 2016 at 4:15:32 PM UTC+2
public_elb_dns_name: loopclientstag-ELB-BO61ICKJQBE4-841110159.eu-west-1.elb.amazonaws.com
Comment 5•10 years ago
|
||
==========
POST DEPLOYMENT
==========
loop.server value set to https://loop.stage.mozaws.net/v0
end-2-end test calls (shared URL) - OK
Video/audio mute/unmute - OK
messaging - OK
Tab & window-sharing - OK
privacy & ToS links - OK
Feedback screens - OK
push notifications - OK
URL checks against expected values pass:
----------
deployment_tests/test_deployment.py::test_header PASSED
deployment_tests/test_deployment.py::test_server_config PASSED
deployment_tests/test_deployment.py::test_server_response PASSED
----------
deployment_tests/test_deployment.py::test_push_server_config PASSED
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•