Deploy BigTent to stage with train-2013.01.17 Release 17

RESOLVED FIXED

Status

Cloud Services
Operations: Deployment Requests
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ozten, Assigned: gene)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

5 years ago
+++ This bug was initially created as a clone of Bug #848130 +++

Release 17 has an emergency production hotfix for https://github.com/mozilla/browserid-bigtent/issues/186 which should improve the UX for our users who can't figure out what their Yahoo email address is.

SHA: fee6d772086f678062c459ca1418448dc767d40e
tree: https://github.com/mozilla/browserid-bigtent/tree/train-2012.01.17
The tree is of course (s/2012/2013/):
> tree: https://github.com/mozilla/browserid-bigtent/tree/train-2013.01.17
removing old dependencies from the clone. Less spam going forward.
No longer blocks: 850473, 851524, 852746, 853238, 854596
No longer depends on: 848130
build command: 
> [jrgm@r6.build.mtv1.svc interim-tools]$ ./build.sh browserid-bigtent train-2013.01.17 fee6d772086f678062c459ca1418448dc767d40e 114414

output RPM on r6:
> /home/jrgm/workspace/browserid-bigtent/rpmbuild/RPMS/x86_64/browserid-bigtent-0.2013.01.17-17.el6_114414.x86_64.rpm

I've done a trial deploy to traditional physical scl2 stage, but I can't test it there. Gene will need to deploy to aws stage tomorrow to give it a smoketest there.
Assignee: nobody → gene
(Assignee)

Comment 4

5 years ago
stage is updated
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
curl https://yahoo.login.anosrep.org/ver.txt =>

fee6d77 Merge pull request #191 from mozilla/issue-186-mismatch-expose-error
locale svn r114414

This works on the stage instance, and I get content like https://github.com/mozilla/browserid-bigtent/issues/186#issuecomment-16266978

This is good to go to production, but I'm not sure this is the greatest time to push it out.
Actually QA signs off on this build going to production - See https://bugzilla.mozilla.org/show_bug.cgi?id=861411
You need to log in before you can comment on or make changes to this bug.