Closed Bug 920990 Opened 11 years ago Closed 11 years ago

please deploy browserid train-2013.09.25 to stage

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: stomlinson, Assigned: gene)

Details

sha: fd35c10fdf20b96febd53d571d2d468c1ec9ec1c

ChangeLog: https://github.com/mozilla/browserid/blob/train-2013.09.25/ChangeLog#L3-L14

Schedule: http://personatra.in/#2013.09.25

Areas to concentrate testing:
* Ensure that iOS7 users are not signed out when refreshing the RP's page
* Ensure that certs are not requested from the fallback IdP for addresses supported by primary IdPs
* Ensure RP branding (siteLogo and backgroundColor) are set for all four verification emails.
* Ensure RP branded emails look visually correct across a variety of email clients.
Assignee: nobody → jrgm
I've built the rpm for browserid train-2013.09.25

output rpm on r6:
/home/jrgm/workspace/browserid/rpmbuild/RPMS/x86_64/browserid-server-0.2013.09.25-1.el6_120983.x86_64.rpm

Build command:
sh -x ./build.sh browserid train-2013.09.25 fd35c10fdf20b96febd53d571d2d468c1ec9ec1c

md5sum of rpm: 878e9a52bd58c4b2605ebad5911558cd

Gene, please build a stack in stage with the above rpm, if you have a chance.
Assignee: jrgm → gene
Flags: needinfo?(gene)
Status: NEW → ASSIGNED
Flags: needinfo?(gene)
Stack 1010 is built and DNS has been switched to it in staging.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I've not idea if this relates to this build, but when I try to log into staging with an @mozilla.com address, persona times out trying to provision. Does it localize to talk to a different MozIDP maybe? When I try mockmyid.com in stage it works fine and when I try mozidp in prod it works fine.

This may be a red herring but thought I'd mention that I noticed it.
Gene: so, if you use an @mozilla.com address in stage, that will try to use the production login.mozilla.org bridge, and that will timeout due to cross-origin problems. That is expected. 

To use mozidp in stage, if you enter someone@test-moz-idp.com, that will use login.allizom.org, and an extra trick is trown in so that it changes the email address to someone@mozilla.com, and then can validate you. This is only a testing workaround for stage, of course.
Got it, thanks for the clarification.
You need to log in before you can comment on or make changes to this bug.