Confirmed users
1,158
edits
EngineeringProductivity/HowTo/SignExtensions: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/HowTo/SignExtensions (view source)
Revision as of 23:23, 2 June 2017
, 2 June 2017no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
'''Update: June 2017''' | |||
In the Add-on manager now checks isInAutomation to see if Firefox is running in the test suite or not. If it is, then the signing checks are bypassed. Meaning that '''most of this document is now no longer relevant'''. All new tests should not need to sign an add-on. There might be some old tests that are still affected. | |||
---- | |||
With the new addon signing requirement, working with addons in mozilla-central gets a little more complicated. Anytime an addon is modified, it will need to be version bumped and re-signed. Yes, even if you just want to add a dump statement to debug a try run. Yuck! This guide is intended to provide all the information you need to work with signed addons in mozilla-central. At first, signing will largely be a manual process, but eventually tooling will improve and the process will get easier. | With the new addon signing requirement, working with addons in mozilla-central gets a little more complicated. Anytime an addon is modified, it will need to be version bumped and re-signed. Yes, even if you just want to add a dump statement to debug a try run. Yuck! This guide is intended to provide all the information you need to work with signed addons in mozilla-central. At first, signing will largely be a manual process, but eventually tooling will improve and the process will get easier. | ||