Configure select background tasks to enable Nimbus experiments and Firefox Messaging System (and Messaging Experiments)
Categories
(Toolkit :: Background Tasks, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox104 | --- | fixed |
People
(Reporter: nalexander, Assigned: nalexander)
References
(Depends on 2 open bugs, Blocks 3 open bugs)
Details
(Whiteboard: [fidedi-notifications])
Attachments
(1 file, 1 obsolete file)
This is "the work" for Bug 1764603 and Bug 1775133.
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
This commit does several things:
-
It configures a new Nimbus feature and corresponding message group
backgroundTaskMessage
. -
It configures a new
background-task-message
Firefox Messaging
System provider specific to background tasks. It is a
remote-settings
provider that uses a new bucket
background-task-message
, and that usesRemoteL10n
. -
It configures
Firefox Messaging Experiments
to use a new
nimbus-desktop-background-task-experiments
Remote Settings
collection, sibling to the existingnimbus-desktop-experiments
collection.
These configurations are achieved by setting preferences in
backgroundtasks.js
, which is applied on top of firefox.js
prefs by
the preference service. These preferences apply to every background
task.
-
It implements functions for enabling Nimbus and the Firefox
Messaging System (and Messaging Experiments) that can be used by
arbitrary background tasks.It is assumed (but not enforced here) that such tasks will use
non-ephemeral (persistent) profiles, so that Remote Settings
incremental sync, Nimbus bucketing, and Messaging System message
limits, function as expected. -
It adds a new
message
background task specifically for testing
background task messages. Invoke the testing task with command
lines likefirefox --backgroundtask message ...
.To ease testing, the framework accepts
--url about:studies?...
arguments from the Experimenter Web UI to explicitly opt-in to
specific experiment branches.
Eventually the existing backgroundupdate
task will use the new
functions, just as the testing message
task does.
Depends on D150217
Assignee | ||
Comment 2•2 years ago
|
||
There is a single nalexander-ms-test1
experiment defined: see
https://stage.experimenter.nonprod.dataops.mozgcp.net/nimbus/nalexander-ms-test1
Because of the way that Nimbus/Experimenter publishes previews, the
collection needs to be overridden to be nimbus-preview
. This is
what happens for regular Desktop experiment previews as well.
That single experiment should be fetched, complete enrollment, and pop
a toast notification. The title string of the toast notification
shows the treatment group, A or B, and the body string of the toast
notification uses RemoteL10n or is an in-product string, respectively.
Depends on D150522
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Backed out for causing failure at browser_all_files_referenced.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/2174465e14880c21e5fa0e63aacd7bd1eff5fe5a
Failure log: https://treeherder.mozilla.org/logviewer?job_id=385062798&repo=autoland&lineNumber=2705
Comment 7•2 years ago
|
||
Backed out for causing failures at browser_all_files_referenced.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/359e12a89f139443d66898e2e15f798e9d557f93
Failure log: https://treeherder.mozilla.org/logviewer?job_id=385084308&repo=autoland&lineNumber=2625
Comment 9•2 years ago
|
||
bugherder |
Assignee | ||
Comment 10•2 years ago
|
||
Clearing NI since this has been addressed.
Description
•