Closed
Bug 784553
Opened 13 years ago
Closed 13 years ago
Update SDK data for SDK release 1.10
Categories
(addons.mozilla.org Graveyard :: Add-on Validation, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2012-09-13
People
(Reporter: canuckistani, Assigned: KWierso)
References
Details
Basta: I'm logging bugs for 1.10 super early because I have some PTO coming up. Please ignore for now.
On Wednesday Sept 12, the Wes issue a pull request containing the signatures for the 1.10 tag and include it in this bug.
| Assignee | ||
Comment 1•13 years ago
|
||
https://github.com/mozilla/amo-validator/pull/182 has the new hashes, and I verified that the 1.10 tag is in there.
It would be really good to have this in tomorrow's push so everything is set up for next week's release of 1.10 to the world.
Target Milestone: --- → 2012-09-13
Comment 2•13 years ago
|
||
This will be pushed tomorrow:
https://github.com/mozilla/amo-validator/commit/25876ddb5153b9846bcb26391374a2f0cede8147
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•13 years ago
|
||
I just submitted a 1.10 addon built from Builder to the validator, and it's claiming I'm using a future version of the SDK that isn't in the validator. I could've sworn this was working when I tested it last week, though.
Did a bunch of stuff get backed out of production or something?
https://addons.mozilla.org/en-US/developers/upload/f3f51457b3534df28d536f1d1fd7cd02
According to that addon's harness-options.json file, it claims to be using sdkVersion 1.10, not anything weird like 1.10-dev or 1.10rc2.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•13 years ago
|
||
We landed a change that pickled the hash file shortly before the hashes were updated. I didn't think to check for an update to the pickle file, so it still thinks we're on 1.9. cvan is working to see if we can push the updated pickle file to prod now.
https://github.com/mozilla/amo-validator/commit/a61300a32afd0601862e389309d70b90402eb49b
The update script was been updated to compensate for this, but it doesn't look like the new version was used. Make sure in the future that you run the shell script to generate hashes on a branch that's up-to-date with master and also make sure that the script exits with a status code of 0.
Sorry for the confusion!
Comment 5•13 years ago
|
||
Fixed and pushed to production:
https://github.com/mozilla/zamboni/commit/3b1fcd5
Sorry for the inconvenience!
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•