Closed
Bug 960284
Opened 10 years ago
Closed 10 years ago
please deploy browserid train-2013.10.23 to production
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jrgm, Assigned: gene)
References
Details
Gene: Now, new and improved. Please build browserid-server with sha 3c066b17681f09f86c49e0080d757058348643ad and locale svn version 122101, from the browserid_private repo (on the train-2013.10.23, to be complete). And then build a __production__ stack with that rpm.
Assignee | ||
Comment 1•10 years ago
|
||
Stacks 0121 are up in both datacenters. Take a look and I'll put traffic on them.
Flags: needinfo?(jrgm)
Comment 2•10 years ago
|
||
jrgm and karl are looking at it.
Reporter | ||
Comment 3•10 years ago
|
||
Gene: you can switch DNS traffic to the 0121 stacks.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(jrgm)
Assignee | ||
Comment 5•10 years ago
|
||
2:46pm stacks 0121 have been brought live in DNS
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(gene)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•10 years ago
|
||
John report marketplace issues. 4:55pm PST I rolled back to 1203 stacks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 7•10 years ago
|
||
It looks like a problem with this security fix: https://github.com/mozilla/browserid_private/commit/11e48d48b7eb75b674408a71159c696fe711368d I have not yet been able to reproduce the problem with Marketplace, but if removing the above commit fixes it, I think we should just push that security fix to the next train and push that revised stack to prod.
Comment 8•10 years ago
|
||
:gene, please build a production stack from SHA 2be2d217c93e6a12e74bd59eb48edaa64601d797 in browserid_private, and locale svn version 122101. Thank you, -Callahad
Flags: needinfo?(gene)
Comment 9•10 years ago
|
||
Gene: can you update us on your status on this so QA can schedule testing and prod deploy. Thanks.
Assignee | ||
Comment 10•10 years ago
|
||
I'm planning to build these stacks today. :callahad's request came in at 8:44pm Friday night and I had not seen it until now, Monday morning.
Assignee | ||
Updated•10 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 11•10 years ago
|
||
To clarify, this from a different branch Commit : 2be2d217c93e6a12e74bd59eb48edaa64601d797 Branch : train-2013.10.23-release
Flags: needinfo?(gene)
Comment 12•10 years ago
|
||
Yep! Sorry I didn't make that clear. Thanks!
Assignee | ||
Comment 13•10 years ago
|
||
Stacks 0127 are up in both datacenters. QA, take a look
Reporter | ||
Comment 14•10 years ago
|
||
:callahad - not understanding what is being shipped here. Tests do not pass. $ git symbolic-ref --short -q HEAD ; git rev-parse --short HEAD train-2013.10.23-release 2be2d21 $ node tests/unverified-email-test.js Setting NODE_ENV to test_json to test with the local JSON database To test with a local mysql database, setup mysql and set NODE_ENV to test_mysql · · · ···· · · ·· ·verifier (86283): error: uncaughtException: Object #<Object> has no method 'currentSupport' ... ... stack=[TypeError: Object #<Object> has no method 'currentSupport', at /Users/jmorrison/github/mozilla/browserid_private/lib/verifier/certassertion.js:183:19, at /Users/jmorrison/github/mozilla/browserid_private/node_modules/jwcrypto/lib/cert.js:183:7 · Closing this bug. File a new ticket.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → INVALID
Comment 15•10 years ago
|
||
This train is cursed. There's been a ridiculous amount of cherry-picking in the commit graph, and it's making it hard for us to reason about what we're actually doing. The lack of Travis on the private repo also bit us, as John found. francois: I suggest we abandon 2013.10.23 (change this from INVALID to WONTFIX) and prepare a new train based on the current tip of the dev branch. Since you proposed a new release process, I'll leave the abandon/fix-again decision to you.
Flags: needinfo?(francois)
Comment 16•10 years ago
|
||
While I agree that this train has run into a lot of problems, adding more changes to it (i.e. getting all of the stuff that's on dev but not on 10.23) is only going to make things worse. It sounds like we forgot to fix the test suite after we reverted the commit that broke forceIssuer, so that should be fairly easy to fix.
Flags: needinfo?(francois)
Assignee | ||
Comment 17•10 years ago
|
||
I've torn down stacks 0127 in both datacenters
Assignee | ||
Updated•10 years ago
|
Resolution: INVALID → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•