Closed
Bug 1261915
Opened 8 years ago
Closed 8 years ago
Please deploy autopush 1.14.1 to PRODUCTION
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cloud-services-qa, Assigned: oremj)
References
Details
------------------ RELEASE NOTES ------------------ https://github.com/mozilla-services/autopush/releases COMPARISONS https://github.com/mozilla-services/autopush/compare/1.13.1...1.13.2 https://github.com/mozilla-services/autopush/compare/1.13.2...1.14.0 https://github.com/mozilla-services/autopush/compare/1.14.0...1.14.1 TAGS https://github.com/mozilla-services/autopush/releases/tag/1.14.1 https://github.com/mozilla-services/autopush/commit/db51c6a6711e67afe96d761829e4129cb5acbecc CHANGELOG <a name="1.14.1"></a> ## 1.14.1 (2016-03-28) #### Chore * tag 1.14.1 ([8cf95035](https://github.com/mozilla-services/autopush/commit/8cf950355ee08421cc48aeebaa7d4427864fcb54)) #### Bug Fixes * update cffi dep and ensure test reqs matches reqs ([669e1b24](https://github.com/mozilla-services/autopush/commit/669e1b244cf5412df604059da27bdf850446b487))
Comment 1•8 years ago
|
||
here's what's on PRODUCTION pre-deployment.... ---------------------------- URL CHECKS (PROD) ---------------------------- https://push.services.mozilla.com: Response time: 0.116975 https://updates.push.services.mozilla.com/health: { "status": "OK", "prod.autopush.routerv2": { "status": "OK" }, "prod.autopush.storage": { "status": "OK" }, "version": "1.13.2", "clients": 0 } Response time: 0.15307 https://updates.push.services.mozilla.com/status: { "status": "OK", "version": "1.13.2" } Response time: 0.118416
Comment 2•8 years ago
|
||
cache-test ready. We'll be deploying autopush 1.14.1 to PRODUCTION today @ 1:30p PST
Comment 3•8 years ago
|
||
:oremj has deployed new (1.14.1) release to production ---------------------------- URL CHECKS (PROD) ---------------------------- https://push.services.mozilla.com: Response time: 0.122154 https://updates.push.services.mozilla.com/health: { "status": "OK", "prod.autopush.routerv2": { "status": "OK" }, "prod.autopush.storage": { "status": "OK" }, "version": "1.14.1", "clients": 0 } Response time: 0.150154 https://updates.push.services.mozilla.com/status: { "status": "OK", "version": "1.14.1" } Response time: 0.130767
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 4•8 years ago
|
||
---------------------------- TEST SUMMARY ---------------------------- ap-loadtester basic scenario and end-to-end push tests passing. Verifying this release (tests outlined below) ---------------------------- SCENARIO TESTING ---------------------------- AP-LOADTESTER: SCENARIO TESTING Run the following scenarios from https://github.com/mozilla-services/ap-loadtester/ * basic ---------------------------- E2E-TESTS ---------------------------- FINDMYDEVICE Able to successfully ring and lock STAGE-configured Flame device (w/ B2G 2.2) x10 HELLO FIREFOX Able to place several Hello (Loop) calls successfully between Nightly (48.0a1) and Gen Release (45.0.1) w/ STAGE autopush and verify e2e test calls, room notifications - OK DESKTOP E2E PUSH TEST setup: start browser with new profile open: about:config set: dom.push.loglevel=debug (instead of 'off') open: Tools > WebDeveloper > BrowserConsole open: https://people.mozilla.org/~ewong2/push-notification-test/ choose: "service-worker.js" click: "register Service Worker" click: "subscribe to push" observe push registration in console click: "Always Receive Notifications" (in pop-up window) 1. registration test steps: click: "XHR to webpush app-server" observe: successful registration in console 2. message delivery test setup: set: Repeat = 2 set: Delay (seconds) = 15 steps: click: "XHR to webpush app-server" observe: 2 pop notifications 15 seconds apart 3. payload test setup: set: Title = PAYLOAD TEST set: Body = BODY TEXT HERE set: TTL = 120 set: Repeat = 4 set: Delay (seconds): 20 steps: click: "XHR to webpush app-server" observe: should see delayed pop notifications with Title, Body specified 4. storage test purpose: verify that a request is stored on autopush for delayed delivery setup: (same as 3 above) steps: click: "XHR to webpush app-server wait for pop notification, then immediately close browser wait 25 seconds re-open browser observe: should see 3 more delayed messages delivered on browser restart
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•