Opened on 12/05/2016 at 08:46:14 AM
Closed on 12/05/2016 at 11:01:47 AM
#4700 closed change (fixed)
Allow specifying devbuilds update URL in manifest.json for WebExtensions builds
| Reported by: | trev | Assignee: | trev |
|---|---|---|---|
| Priority: | P3 | Milestone: | |
| Module: | Automation | Keywords: | |
| Cc: | sebastian, kzar | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by trev)
Background
With #4697 we will be producing Gecko development builds outside of AMO again. These need to be updated via our server, not AMO.
What to change
Add support for updateURL and devbuildUpdateURL configuration options (section [general]) to packagerChrome. If these options are present, an update_url value should be added to manifest.json under applications for the release and development builds respectively. See https://developer.mozilla.org/en-US/Add-ons/Updates for details on the expected format.
Attachments (0)
Change History (5)
comment:1 Changed on 12/05/2016 at 08:52:57 AM by trev
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:2 Changed on 12/05/2016 at 08:59:31 AM by trev
- Description modified (diff)
- Summary changed from Allow specifying devbuilds update URL in manifest.json to Allow specifying devbuilds update URL in manifest.json for WebExtensions builds
comment:3 Changed on 12/05/2016 at 10:34:54 AM by kzar
- Priority changed from Unknown to P3
- Ready set
comment:4 Changed on 12/05/2016 at 11:01:04 AM by abpbot
comment:5 Changed on 12/05/2016 at 11:01:47 AM by trev
- Resolution set to fixed
- Status changed from reviewing to closed
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 4700 - Allow specifying devbuilds update URL in manifest.json for WebExtensions builds