Firefox/Go Faster/Releasing an add-on mechanics: Difference between revisions
Jump to navigation
Jump to search
Warning: This document and process is still in a very active exploration and discovery phase. It has not been tested fully, and may change at any time. ianb and Standard8 know most about the process
Warning: This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.
(Initial version, dump the know notes so far.) |
(Update ftp details and basic access information.) |
||
| Line 3: | Line 3: | ||
{{warning|This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.}} | {{warning|This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.}} | ||
* | This document only contains details about the mechanics for releasing. You will need to discuss with release drivers and other folks about being able to actually do a release. | ||
* Upload xpi to ftp | |||
== Access Rights == | |||
To upload and release add-ons, you'll need access to: | |||
* ftp (<code>[https://ftp.mozilla.org/pub/system-addons/ /pub/system-addons/]</code>) | |||
** Talk to the Cloud Services team for access | |||
* balrog via VPN | |||
** Talk to Release Engineering team for access | |||
== Procedure | |||
This process assumes you have a xpi that is ready for release. | |||
* Get the xpi signed, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1249764 clone this bug] | |||
* Upload the signed xpi to ftp in the <code>[https://ftp.mozilla.org/pub/system-addons/ /pub/system-addons/]</code> directory. | |||
** Use a sub-directory appropriate for the add-on. | |||
* Generate Balrog template | * Generate Balrog template | ||
** Under Releases, search for `SystemAddons` | ** Under Releases, search for `SystemAddons` | ||
Revision as of 10:14, 25 February 2016
Warning: This document and process is still in a very active exploration and discovery phase. It has not been tested fully, and may change at any time. ianb and Standard8 know most about the processWarning: This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.This document only contains details about the mechanics for releasing. You will need to discuss with release drivers and other folks about being able to actually do a release.
Access Rights
To upload and release add-ons, you'll need access to:
- ftp (
/pub/system-addons/)- Talk to the Cloud Services team for access
- balrog via VPN
- Talk to Release Engineering team for access
== Procedure
This process assumes you have a xpi that is ready for release.
- Get the xpi signed, e.g. clone this bug
- Upload the signed xpi to ftp in the
/pub/system-addons/directory.- Use a sub-directory appropriate for the add-on.
- Generate Balrog template
- Under Releases, search for `SystemAddons`
- Download the existing template
- Update fileUrl, default https
- Update the hashValue (`shasum -a 512 <file>`)
- Update filesize (bytes, `ls -la <file>`)
- Update version
- Update name if necessary
- Upload template to either updated release or new release.
- Under Rules, search for `SystemAddons`
- Create/Update as necessary
- Example update url `https://aus5.mozilla.org/update/3/SystemAddons/45.0/20160218171844/default/en-US/beta-cdntest1/default/default/default/update.xml`