Closed
Bug 1225304
Opened 10 years ago
Closed 10 years ago
Please deploy autopush 1.8.1 to STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jrconlin, Assigned: oremj)
References
Details
https://github.com/mozilla-services/autopush/releases/tag/1.8.1
Note: Configuration change required::
please include in .autopush_endpoint
auth_key=[key]
Where key is a value generated from bin/autokey
This value is used to derive the bearer token value.
Comment 1•10 years ago
|
||
(In reply to JR Conlin [:jrconlin,:jconlin] from comment #0)
> https://github.com/mozilla-services/autopush/releases/tag/1.8.1
>
> Note: Configuration change required::
>
> please include in .autopush_endpoint
>
> auth_key=[key]
>
> Where key is a value generated from bin/autokey
>
> This value is used to derive the bearer token value.
Just finished testing 0.8.0. Do we need to skip 0.8.0 and move ahead with 1.8.1?
Flags: needinfo?(jrconlin)
Assignee | ||
Comment 2•10 years ago
|
||
1.8.1 has been deployed to STAGE.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
spoke w/ JR. dropping 1.8.0 and moving forward with this release
----------------------------
SUMMARY
----------------------------
unittests - OK
.............
E2E TESTS
.............
DESKTOP PUSH NOTIFICATIONS
FINDMYDEVICE
Able to successfully locate, ring and lock STAGE-configured Flame device (w/ B2G 2.2) x10
HELLO
Able to place several Hello (Loop) calls successfully between Dev Edition (45.0a2) and GR (42) w/ autopush
and verify e2e test calls, room notifications - OK
Verifying STAGE.
----------------------------
SUMMARY
----------------------------
unittests - OK
E2E TESTS
Able to successfully locate, ring and lock STAGE-configured Flame device (w/ B2G 2.2) x10 - OK
Able to place several e2e-test Hello (Loop) calls successfully using desktop Nightly
and verify push using room status changes, pop notifications - OK
Verifying STAGE.
----------------------------
HOST CHECKS (STAGE)
----------------------------
EC2 INSTANCE PROPERTIES
region: us-east-1:
id: i-3b37b385
tags["Type"]: autopush
tags["Stack"]: autopush
public_dns_name: ec2-52-23-209-168.compute-1.amazonaws.com
launch_time: 2015-11-17T00:14:47.000Z
----------------------------
URL CHECKS (STAGE)
----------------------------
https://updates-autopush.stage.mozaws.net/health:
{
"status": "OK",
"stage.autopush.storage": {
"status": "OK"
},
"stage.autopush.router": {
"status": "OK"
},
"version": "1.8.1",
"clients": 0
}
Response time: 0.403164
https://updates-autopush.stage.mozaws.net/status:
{
"status": "OK",
"version": "1.8.1"
}
Response time: 0.353556
Status: RESOLVED → VERIFIED
Flags: needinfo?(jrconlin)
Comment 4•10 years ago
|
||
Ben, do you have the results of the latest loadtest run for autopush and, if so, can you post them here or an etherpad?
Flags: needinfo?(bbangert)
Updated•10 years ago
|
Flags: needinfo?(bbangert)
Comment 5•10 years ago
|
||
I do not have a load-test result at the moment, returning to that work next.
You need to log in
before you can comment on or make changes to this bug.
Description
•