Closed Bug 990393 Opened 11 years ago Closed 11 years ago

please deploy fxa-content and fxa-auth train-08 to stage

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: jrgm, Unassigned)

References

Details

(Whiteboard: [qa+])

... and we already have branches: https://github.com/mozilla/fxa-auth-server/tree/train-08 https://github.com/mozilla/fxa-content-server/tree/train-08 :mostlygeek has some changes for the mock-create.sh rpm build scripts in https://github.com/mozilla-services/svcops/pull/68, which I have used and they work for me. When that lands, I'll re-build the rpms again, and I think there will be a little maintenance required in the yum repo's to remove rpms of the former naming convention.
I'll take care of the yum repo clean up. Basically I'll be deleting all the RPMs that are out of date/improperly named.
are we blocking on #68? can we work around it for testing and re-deploy once #68 lands. I know that pushing this train out during work week is hard.
I built rpms (off the issue58) branch, and built stacks for fxa-auth and fxa-content, and switched DNS to the new stacks in stage. Remote tests pass for auth-server. s3://net.mozaws.ops.rpmrepo-stage/6/x86_64/fxa-auth-server-svcops-0.8.0-1.x86_64.rpm s3://net.mozaws.ops.rpmrepo-stage/6/x86_64/fxa-content-server-svcops-0.8.0-1.x86_64.rpm
TPS matches prod (2 failures) localization emails confirmed 15 min smoke pass - synced bookmarks and themes between 2 profiles. stage: looks good deploy for me.
Blocks: 991790
Closing this bug as TRAIN-08 was a long time ago. :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.