Confirmed users
534
edits
(Add details about creating releases and rules in balrog) |
(→Set up a rule in Balrog: Update testing) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 28: | Line 28: | ||
{{warning|Multiple system add-ons are released together as one bundle which should be tested. Take account of this when updating the template files.}} | {{warning|Multiple system add-ons are released together as one bundle which should be tested. Take account of this when updating the template files.}} | ||
* | When experimenting/doing initial setup, it is suggested to use the dev servers for Balrog: | ||
* https://aus4-admin-dev.allizom.org/ with update urls at https://aus4-dev.allizom.org/update/3/SystemAddons/45.0/20160218171844/default/en-US/beta-cdntest1/default/default/default/update.xml | |||
Once you're confident of the configuration, you can then copy this across to production: | |||
* For production, sign into Balrog at https://aus4-admin.mozilla.org/ | |||
=== Set up a release in Balrog === | |||
First step is to generate the template for the System add-on update release. This contains detail about the xpis, and which platform(s) they are for. | First step is to generate the template for the System add-on update release. This contains detail about the xpis, and which platform(s) they are for. | ||
Line 50: | Line 58: | ||
At this stage, the details for the add-on release have been created. Now you need to create a rule for it to be picked up. | At this stage, the details for the add-on release have been created. Now you need to create a rule for it to be picked up. | ||
=== Set up a rule in Balrog === | |||
{{warning|Rules go live as soon as they are created or updated.}} | {{warning|Rules go live as soon as they are created or updated.}} | ||
Line 65: | Line 75: | ||
** You can use the results to check your expectations of values to put in fields. | ** You can use the results to check your expectations of values to put in fields. | ||
* Select "Add a new rule" | * Select "Add a new rule" | ||
** More background on rules at [[Balrog#What.27s_in_a_rule.3F|Balrog pages]] | |||
** Leave blank: Alias, Locale, Distribution, Build Target, OS Version, Dist Version, Whitelist, Header Architecture | ** Leave blank: Alias, Locale, Distribution, Build Target, OS Version, Dist Version, Whitelist, Header Architecture | ||
** Product: <code>SystemAddons</code> | ** Product: <code>SystemAddons</code> | ||
Line 78: | Line 89: | ||
The changes are live within a few seconds. | The changes are live within a few seconds. | ||
=== Verifying Balrog === | |||
Testing via url: | Testing via url: | ||
* You can check the data via a url: https://aus5.mozilla.org/update/3/SystemAddons/ | * You can check the data via a url: https://aus5.mozilla.org/update/3/SystemAddons/49.0.1/20160922113459/default/en-US/release-sysaddon/default/default/default/update.xml | ||
** You'll need to replace the version, build id and maybe the channel in the url above. | ** You'll need to replace the version, build id and maybe the channel in the url above. | ||
Testing in Firefox: | Testing in Firefox: | ||
* Note: currently system add-ons updates don't apply until you restart Firefox. | * Note: currently system add-ons updates don't apply until you restart Firefox. | ||
* | * In `about:config` open `extensions.systemAddon.update.url` and change %CHANNEL% to `release-sysaddon` | ||
* Add-on manager activity can be monitored by setting <code>extensions.logging.enabled</code> to true. | * Add-on manager activity can be monitored by setting <code>extensions.logging.enabled</code> to true. | ||
* You can force an add-on update with the [https://addons.mozilla.org/en-US/firefox/addon/timer-fire/ timer-fire add-on] | * You can force an add-on update with the [https://addons.mozilla.org/en-US/firefox/addon/timer-fire/ timer-fire add-on] |