Closed
Bug 699606
Opened 14 years ago
Closed 14 years ago
Adjust the data AMO sends to the repackager API
Categories
(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P1)
addons.mozilla.org Graveyard
Admin/Editor Tools
Tracking
(Not tracked)
RESOLVED
FIXED
6.3.3
People
(Reporter: clouserw, Assigned: kumar)
References
Details
In files.tasks.start_upgrade we POST a bit of data to builder.amo about what jetpacks to repack when a new SDK version comes out. Right now we send it the URL to a file, builder downloads it, extracts it, etc.
The new process has us sending an ID and the builder will rebuild with the knowledge it holds rather than parsing out an existing .xpi (should be much more reliable.
In bug 699519 we store a value that is sent from the builder (the package revision primary key). This bug is about:
- Adding that package revision primary key to the POSTed data
- Removing the 'location'
| Reporter | ||
Comment 1•14 years ago
|
||
Let's call the new field "package_key"
| Reporter | ||
Updated•14 years ago
|
Assignee: nobody → kumar.mcmillan
Priority: -- → P1
Target Milestone: --- → 6.3.3
| Assignee | ||
Comment 2•14 years ago
|
||
Fixed: https://github.com/mozilla/zamboni/commit/e1990fd
If it's a new style jetpack with builderVersion in its harness then package_key is part of the POST. Otherwise, it falls back to posting the location field.
Status: NEW → RESOLVED
Closed: 14 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
•