Closed
Bug 1544751
Opened 6 years ago
Closed 6 years ago
Glean: Make sure experiments enable & disable correctly on init & updates
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gfritzsche, Assigned: travis_)
References
Details
(Whiteboard: [telemetry:mobilesdk:m7])
Attachments
(1 file)
This will require some code review, testing and code changes.
- Make user
ActiveExperiment.clear()
is called in the right places. - Make sure that, on library init:
- The cached active experiment is initiated.
- But not if it's matchers don't apply anymore, and the active experiment cache is cleared.
- If there is no active experiment yet, that the cached experiments list is evaluated and the first matching experiment is started.
- On experiments update:
- The experiment list is evaluated and...
- If there is no active experiment, the first matching experiment is started and cached.
- If there is an active experiment, it is stopped and cache cleared if it was deleted from the list.
- ... more?
Reporter | ||
Updated•6 years ago
|
Type: defect → task
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
It might be good to use a Kinto dev setup here to check things are wired up correctly.
I have a first working pass on the JSON schema and UI schema here:
https://gist.github.com/georgf/cbf4c145ca0e202ad0d25a5a83e06f38
This can be used to create a collection "mobile-experiments" in the "main" bucket on Kinto dev here:
https://kinto.dev.mozaws.net/v1/admin/
Updated•6 years ago
|
Priority: -- → P3
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → gfritzsche
Priority: P3 → P1
Reporter | ||
Comment 2•6 years ago
|
||
I'm currently collecting changes for this in this branch:
https://github.com/georgf/android-components/tree/smoke-test
Updated•6 years ago
|
Component: Telemetry → Glean: SDK
Product: Toolkit → Data Platform and Tools
Reporter | ||
Updated•6 years ago
|
Assignee: gfritzsche → tlong
Assignee | ||
Comment 3•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•