Closed Bug 1161415 Opened 9 years ago Closed 9 years ago

please deploy fxa-{content,auth,oauth,profile} train-36 to production

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jrgm, Assigned: ckolos)

Details

(Whiteboard: [qa+])

Hi Chris,

Please deploy production stacks for fxa-{content,auth,oauth,profile} train-36    

fxa-c-s-train-36-83
fxa-a-s-train-36-71
fxa-o-s-train-36-70
fxa-p-s-train-36-51

NOTE: As discussed, the fxa-content-server MUST go live in DNS before the
fxa-oauth-server goes live in DNS. Despite 60s TTL on those records, we 
should probably allow much more time for misbehaving clients and caches.    

Expected versions:
    
$ curl -s https://accounts.stage.mozaws.net/ver.json; echo; \
  curl -s https://api-accounts.stage.mozaws.net/; echo; \
  curl -s https://oauth.stage.mozaws.net/; echo; \
  curl -s https://profile.stage.mozaws.net/; echo
    
{"version":"0.36.3","commit":"25dedeb0b1f2d5212f34e41ed17317bc5fbf5477","l10n":"412fdf2ec9","tosPp":"15e58d3fe8"}
{"version":"1.36.0","commit":"c369baa3926e554a38ba0d46bf55fd979b8f7338"}
{
  "version": "0.36.1",
  "commit": "fc200c605f5797b17ca78dee4efbd69d883507ff"
}
{
  "version": "0.36.0",
  "commit": "6441e24d4d54ef58a8adb65fb5e042513615db0f"
}
deployed
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.