Closed Bug 1251349 Opened 10 years ago Closed 10 years ago

Please deploy autopush 1.12.1 to PRODUCTION

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rpapa, Assigned: oremj)

References

Details

Assignee: nobody → oremj
Status: NEW → ASSIGNED
Depends on: 1251292
QA Contact: rpappalardo
We'll be deploying this release to production today (Thur., 2/25) @2p PST
here's what's currently in production (pre-deployment): ---------------------------- URL CHECKS (PROD) ---------------------------- ~ ᐅ curl https://updates.push.services.mozilla.com/health | python -m json.tool { "clients": 0, "prod.autopush.routerv2": { "status": "OK" }, "prod.autopush.storage": { "status": "OK" }, "status": "OK", "version": "1.11.0" } ~ ᐅ curl https://updates.push.services.mozilla.com/status | python -m json.tool { "status": "OK", "version": "1.11.0" }
---------------------------- SUMMARY ---------------------------- :oremj has pushed this release to production and all verifciation tests look good. :rpapa will recheck at end of day and verify no issues found. ---------------------------- VERIFICATION TESTS ---------------------------- all verification tests passing. (tests outlined below) 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 (47.0a1) and GR (44.0.2) w/ PRODUCTION autopush and verify e2e test calls, room notifications - OK AP-LOADTESTER: BASIC SCENARIO TEST ran basic scenario w/ ap-loadtester NOTE: this is not a loadtest at scale https://github.com/mozilla-services/ap-loadtester - 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 = 2 set: Delay (seconds): 15 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 30 seconds re-open browser observe: should see delayed message delivery on browser restart NOTE: outlining desktop push tests here for now. eventually move to readthedocs. ---------------------------- URL CHECKS (PROD) ---------------------------- ~ ᐅ curl https://updates.push.services.mozilla.com/health | python -m json.tool { "clients": 0, "prod.autopush.routerv2": { "status": "OK" }, "prod.autopush.storage": { "status": "OK" }, "status": "OK", "version": "1.12.1" } ~ ᐅ curl https://updates.push.services.mozilla.com/status | python -m json.tool { "status": "OK", "version": "1.12.1" }
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
further e2e testing OK. verifying this release.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.