Confirmed users
586
edits
QA/Telemetry/Developing a Telemetry Experiment: Difference between revisions
Jump to navigation
Jump to search
QA/Telemetry/Developing a Telemetry Experiment (view source)
Revision as of 14:38, 10 May 2016
, 10 May 2016→Signing the XPI: Link to signing API docs as well
(Split out separate sections on beta testing, code review, signing) |
(→Signing the XPI: Link to signing API docs as well) |
||
| Line 111: | Line 111: | ||
== Signing the XPI == | == Signing the XPI == | ||
For testing on a stock Beta build, or for deployment, you'll need to have the experiment signed. Once {{bug|1271440}} is fixed, you can use the '''jpm''' tool to sign the experiment, using the instructions at [[EngineeringProductivity/HowTo/SignExtensions|How to Sign Extensions]]. | For testing on a stock Beta build, or for deployment, you'll need to have the experiment signed. Once {{bug|1271440}} is fixed, you can use the '''jpm''' tool to sign the experiment, using the instructions at [[EngineeringProductivity/HowTo/SignExtensions|How to Sign Extensions]]. There is additional documentation on the signing API at [http://addons-server.readthedocs.io/en/latest/topics/api/signing.html] - the '''jpm''' tool uses this infrastructure with a shared automation signing key that your LDAP gives you access to. | ||
Until that bug is fixed, you can file a bug against the addons.mozilla.org product, Addon Validation component, attach the xpi file, and request that it be signed. Ping Jason Thomas if you run into problems. | Until that bug is fixed, though, you can file a bug against the addons.mozilla.org product, Addon Validation component, attach the xpi file, and request that it be signed. Ping Jason Thomas if you run into problems. | ||
== Deploying to staging == | == Deploying to staging == | ||