Closed Bug 1024222 Opened 9 years ago Closed 9 years ago

Deploy release 0.9.2 to loop-server Production

Categories

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

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jbonacci, Assigned: mostlygeek)

References

Details

(Whiteboard: [qa+]) 

Loop-Server Stage has just been verified with :mostlygeek building/deploying v0.6.0-DEV.

Let's get this in Production.
Blocks: 1019564, 1021891
Depends on: 1022886, 1020596
Whiteboard: [qa+]
Depends on: 1024637
Summary: Deploy Loop-Server v0.6.0 to Production → Deploy Loop-Server v0.6.1 to Production
Once 1024637 has been VERIFIED I will make a change window to deploy this to production.
No longer blocks: 1021891
Depends on: 1024180
Updated as 0.6.1 is almost 24 hours and now obsolete.
Summary: Deploy Loop-Server v0.6.1 to Production → Deploy Loop-Server v0.7.0 to Production
Summary: Deploy Loop-Server v0.7.0 to Production → Deploy Loop-Server 0.8.0-dev to Production
https://github.com/mozilla-services/loop-server/tree/0.9.0
Status: NEW → ASSIGNED
Summary: Deploy Loop-Server 0.8.0-dev to Production → Deploy release 0.9.0 to loop-server Production
Assignee: nobody → bwong
Depends on: 1038675
Depends on: 1038699
Depends on: 1000131
Summary: Deploy release 0.9.0 to loop-server Production → Deploy release 0.9.2 to loop-server Production
From IRC channel: :alexis asks
:bobm can you confirm the nginx configuration for stage is configured to have secure websockets?
Wrong bug, moving that comment over to Stage deploy...
:bobm was able to get this out into Production.

This is what I see:

Browser: https://loop.services.mozilla.com
{"name":"mozilla-loop-server","description":"The Mozilla Loop (WebRTC App) server","version":"0.9.2","homepage":"https://github.com/mozilla-services/loop-server/","endpoint":"https://loop.services.mozilla.com","fakeTokBox":false}

curl https://loop.services.mozilla.com
{"name":"mozilla-loop-server","description":"The Mozilla Loop (WebRTC App) server","version":"0.9.2","homepage":"https://github.com/mozilla-services/loop-server/","endpoint":"https://loop.services.mozilla.com","fakeTokBox":false}

curl -I https://loop.services.mozilla.com
HTTP/1.1 200 OK
Date: Thu, 24 Jul 2014 23:20:22 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 229
Connection: keep-alive
ETag: W/"e5-4167743163"
Timestamp: 1406244022820
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
No red flags from the QA teams. I call that a win.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.