1223601 - Please deploy loop-client 0.22.0 to STAGE

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Mark Banner (:standard8)]

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

COMPARISONS
https://github.com/mozilla/loop-client/compare/0.20.1...0.20.2
https://github.com/mozilla/loop-client/compare/0.20.2...0.21.0
https://github.com/mozilla/loop-client/compare/0.21.0...0.22.0

TAGS
https://github.com/mozilla/loop-client/releases/tag/0.22.0
https://github.com/mozilla/loop-client/commit/d5fe2b18fba43b00a10eb8af6cf0792868242086

CHANGELOG
0.22.0 (2015-11-10)
-------------------
- Bug 1212338 - Move the user's "availability" option to the settings menu as a "turn notifications on/off" in the Loop panel.
- Bug 1212340 - Move the Leave feedback option from the conversation window settings menu to the panel settings menu.
- Bug 1050295 - The extraction script should update the changelog automatically.
- Bug 1213810 - Remove obsolete actions previously associated with direct calls.
- Bug 1213855 - Remove direct call functionality from Loop's backend.
- Bug 1210774 - Upgrade Loop's use of eslint (to 1.6.x) and eslint-plugin-react (to 3.5.x).
- Bug 1212079 - Removed contact scripts from index.
- Bug 1215455 - eslint no-multi-spaces
- Bug 1215455 - eslint object-curly-spacing
- Bug 1215455 - eslint space-after-keywords
- Bug 1215455 - eslint space-before-blocks
- Bug 1215455 - eslint space-before-function-paren
- Bug 1215455 - eslint space-in-parens
- Bug 1215455 - eslint react/jsx-curly-spacing
- Bug 1215455 - eslint consistent-return
- Bug 1213336 - Update Hello standalone npm version.
- Bug 1216551 - Fix an issue with Loop's unit tests failing when no devices are installed, due to bad stubbing.
- Bug 1214582 - Adjust how room titles are displayed/managed in Loop's UI.
- Bug 1212357 - Update the layout of the rooms list items for user journey.
- Bug 1215322 - remove need for CSP unsafe-eval in Hello.
- Bug 1214590 - Remove Loop default Room name.
- Bug 1213906 - Change email invitation to fit new user journey.
- Bug 1215487 - Fix Mozilla logo in Chrome for Loop Standalone
- Bug 1220878 - switch Hello from React.addons.classSet to classnames package.
- Bug 1147167 - Upgrade React in Hello to 0.13.3.
- Bug 1210865 - Update OpenTok library to version 2.6.8.
- Bug 1210865 - Change how Loop's data channels are setup to cope with the newer SDK that doesn't allow setting them up until subscription is complete.
- Bug 1223351 - Store a metrics event on the loop server if the data channel setup fails.

Comment 1

[Mark Banner (:standard8)]

Bob, please also update the CSP reporting to that in bug 1139119 comment 39. Thanks.

Comment 2

[Bob Micheletto [:bobm]]

(In reply to Mark Banner (:standard8) from comment #1)
> Bob, please also update the CSP reporting to that in bug 1139119 comment 39.
> Thanks.

Deployed to stage with the latest CSP updates.

Comment 3

[Richard Pappalardo [:rpapa][:rpappalardo]]

Thanks, Bob!

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

EC2 INSTANCE PROPERTIES
region: eu-west-1: 
id: i-8023b038
tags["Type"]: loop_client
tags["AppGitRef"]: refs/tags/0.22.0
tags["Stack"]: loopclientstage1-loop-client-app-47
public_dns_name: ec2-54-229-207-170.eu-west-1.compute.amazonaws.com
launch_time: 2015-11-11T18:11:46.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-Report-Only: frame-ancestors 'self'; default-src 'self'; img-src 'self' data: https://www.gravatar.com/ https://www.google-analytics.com https://stats.g.doubleclick.net; font-src 'none'; frame-src 'self' https://tiles.cdn.mozilla.net; connect-src 'self' wss://*.tokbox.com https://*.opentok.com https://*.tokbox.com wss://*.mozilla.com https://*.mozila.com https://*.mozilla.org wss://*.mozaws.net https://*.mozaws.net; media-src 'self' blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.optimizely.com https://www.google-analytics.com; style-src 'self' about: 'unsafe-inline'; report-uri /__cspreporting__/
Content-Type: text/html
Date: Thu, 12 Nov 2015 17:34:51 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.007452


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.646997


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.635377


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

Comment 4

[Richard Pappalardo [:rpapa][:rpappalardo]]

:Standard8

Did a few e2e-test calls using DevEd, Nightly and Release.  Looks like push is working on STAGE (the call initiates/ends properly), but the pop notification window doesn't appear on call start (it does on PROD).

Could this be due to CSP change?

Comment 5

[Mark Banner (:standard8)]

As discussed on irc, this seems to be working fine for me on my laptop.

Comment 6

[Richard Pappalardo [:rpapa][:rpappalardo]]

able to verify pop notifications working on different machine.

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

Placed several calls successfully between Dev Edition (45.0a2) and General Release (42.0) using new loop-client tag.

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

unit tests for 0.22.2 release - PASS

Verifying STAGE.