Please deploy loop-client 0.20.2 to STAGE

VERIFIED FIXED

Status

Cloud Services
Operations: Deployment Requests
VERIFIED FIXED
2 years ago
2 years ago

People

(Reporter: standard8, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
------------------
RELEASE NOTES
------------------
https://github.com/mozilla/loop-client/releases

COMPARISONS
https://github.com/mozilla/loop-client/compare/0.19.0...0.20.0
https://github.com/mozilla/loop-client/compare/0.20.0...0.20.1
https://github.com/mozilla/loop-client/compare/0.20.1...0.20.2

TAGS
https://github.com/mozilla/loop-client/releases/tag/0.20.2
https://github.com/mozilla/loop-client/commit/aeb3845a5a2607d26aaa63ec3cc73153ed71e409

CHANGELOG
0.20.2 (2015-09-29)
-------------------

- Bug 1205610 - Log the string associated with OT's UNABLE_TO_PUBLISH exception to help understand where it is coming from.
- Bug 1207575 - Fix reporting of Loop's connection status if a user exits a room and then re-enters it without reloading the room.
- Bug 1200201 - Remove the code for redirecting to the FxOS client from Loop standalone.
- Bug 1199213 - Part 1. Remove the old standalone call-url handling code from Loop.
- Bug 1188509 - Bundle Hello standalone JS for performance.
- Bug 1208647 - minify OpenTok+lodash for faster Hello standalone load time.
- Update L10n
(Reporter)

Comment 1

2 years ago
Note: We need a build process change from this release forwards, we now need to do:

- checkout tag
- make install
- make dist
- package the dist directory

The dist directory has most of js files preprocessed into one, so should reduce requests to the servers, and improve loading performance of the page.
:bobm has deployed this release to stage.
e2e tests look ok, but i'll do final verification tomorrow.

----------------------------
HOST CHECKS (STAGE)
----------------------------

EC2 INSTANCE PROPERTIES
region: eu-west-1: 
id: i-2449f488
tags["Type"]: loop_client
tags["AppGitRef"]: refs/tags/0.20.2
tags["Stack"]: loopclientstage1-loop-client-app-33
public_dns_name: ec2-54-77-235-172.eu-west-1.compute.amazonaws.com
launch_time: 2015-10-02T00:43:59.000Z


PROCESS CHECK

datadog, circus, heka, nginx --> Running!


$ curl -I https://call.stage.mozaws.net:
HTTP/1.1 301 Moved Permanently
Content-Length: 191
Content-Security-Policy: frame-ancestors 'self'
Content-Type: text/html
Date: Fri, 02 Oct 2015 02:40:44 GMT
Location: https://www.mozilla.org/firefox/hello/
X-Frame-Options: SAMEORIGIN
Connection: keep-alive


----------------------------
URL CHECKS (STAGE)
----------------------------

https://call.stage.mozaws.net:
Request was redirected!
status code: 200 --> destination: https://www.mozilla.org/en-US/firefox/hello/

Response time: 0.035635


https://call.stage.mozaws.net/config.js:
var loop = loop || {};

loop.config = {
  serverUrl: 'https://loop.stage.mozaws.net/v0',
  feedbackApiUrl: 'https://input.allizom.org/api/v1/feedback',
  feedbackProductName: 'Loop',
  downloadFirefoxUrl: 'https://www.mozilla.org/firefox/new/?scene=2&utm_source=hello.firefox.com&utm_medium=referral&utm_campaign=non-webrtc-browser\#download-fx',
  privacyWebsiteUrl: 'https://www.mozilla.org/privacy/firefox-hello/',
  legalWebsiteUrl: 'https://www.mozilla.org/about/legal/terms/firefox-hello/',
  marketplaceUrl: 'https://marketplace-dev.allizom.org/iframe-install.html',
  learnMoreUrl: 'https://www.mozilla.org/hello/',
  roomsSupportUrl: 'https://support.mozilla.org/kb/group-conversations-firefox-hello-webrtc',
  guestSupportUrl: 'https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode',
  generalSupportUrl: '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',
  tilesIframeUrl: 'https://tiles.cdn.mozilla.net/iframe.html',
  tilesSupportUrl: 'https://support.mozilla.org/kb/tiles-firefox-hello',
  fxosApp: {
    name: 'Hello Stage',
    manifestUrl: 'https://marketplace-dev.allizom.org/app/ae2af828-21be-4483-ae94-476fe48c6cf8/manifest.webapp',
    rooms: false
  }
};

Response time: 0.872223


https://loop.stage.mozaws.net:
{
    "endpoint": "https://loop.stage.mozaws.net", 
    "name": "mozilla-loop-server", 
    "fakeTokBox": false, 
    "fxaOAuth": true, 
    "version": "0.19.1", 
    "i18n": {
        "defaultLang": "en-US"
    }, 
    "homepage": "https://github.com/mozilla-services/loop-server/", 
    "description": "The Mozilla Loop (WebRTC App) server"
}
Response time: 0.848129


https://loop.stage.mozaws.net/push-server-config:
{
    "pushServerURI": "wss://autopush.stage.mozaws.net"
}
Response time: 0.737965
(Reporter)

Comment 3

2 years ago
I've just done a few checks of my own. The new concatenation seems to be working well and helping to reduce page load times. Compared to production (possibly not quite a true comparison), I'm seeing 3s on prod for a full load, compared to 1s on staging, so its definitely looking promising.
Thanks, Mark.

------------------
SUMMARY (STAGE)
------------------

Placed several calls successfully between Nightly (44.0a1) and General Release (41.0.1) using new loop-client tag.

Noticed inert messaging w/ FxA contact calls in General Release. Per :Standard8, this will be fixed in 42.

see:
Bug 1210843 - Inert messaging area in release browser when messaging during FxA contact call


end-2-end test calls (shared URL) - OK
end-2-end test calls (FxA contacts) - OK
Video/audio mute/unmute - OK
messaging (from Nightly to Nighty) - OK 
Tab & window-sharing - OK
privacy & ToS links - OK
Feedback screens - OK

unit tests for 0.20.2 release - PASS

Verifying STAGE.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Summary: Please deploy 0.20.2 loop-client to stage → Please deploy loop-client 0.20.2 to STAGE
You need to log in before you can comment on or make changes to this bug.