Confirmed users, Bureaucrats and Sysops emeriti
1,737
edits
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
The decision was made that only add-ons from builder.addons.mozilla.org should be able to be automatically upgraded on AMO. Steps to get there: | The decision was made that only add-ons from builder.addons.mozilla.org should be able to be automatically upgraded on AMO. Steps to get there: | ||
* Adjust SDK to allow us to send the builder key/value in package.json | Tracker: {{bug|697863}} | ||
* [{{bug|685378}}] Adjust SDK to allow us to send the builder key/value in package.json | |||
* Add builder identifier to package.json | * Add builder identifier to package.json | ||
** '''What is the identifier called?''' | |||
** '''What is the filepath to package.json?''' | |||
** '''dbuc mentions harness.json in 685378#3 - what is the relationship here?''' | |||
* AMO should pick up on the builder identifier in the package.json | * AMO should pick up on the builder identifier in the package.json | ||
* AMO should only send "builder" add-ons to be repacked via the admin tool | * AMO should only send "builder" add-ons to be repacked via the admin tool | ||
* AMO should only send the necessary data to builder (no longer the file URL) | * AMO should only send the necessary data to builder (no longer the file URL) | ||
** '''What data does builder need?''' | |||
* Builder should only require the necessary data from AMO (no longer the file URL) | * Builder should only require the necessary data from AMO (no longer the file URL) | ||
* Builder should use its knowledge of the add-on to build a new package instead of trying to repack one that AMO sends | * Builder should use its knowledge of the add-on to build a new package instead of trying to repack one that AMO sends | ||