(In reply to Greg Mierzwinski [:sparky] from comment #1)
I've started working on this bug. Here's the patch I have in testing right now: https://hg.mozilla.org/try/rev/7ffef7da2aa3b336bf274091c21862b09cec17d4
Some questions that we need to figure out are:
(1) Can we do manual chrome upgrades rather than automated ones? They would be done at the same time as the other chrome upgrades that we do so it's not adding anything to the process we already have.
We can do this in the short term, but worth looping in :aerickson as would need to be added to any device provisioning procedures that we have. Ultimately I'd like us to automate this.
(2) Name of the android chrome browser is
chrome-m because the perfherder schema limits the number of characters to 10. Should we increase this and make a better name?
Can we just use "chrome"? We can use the platform to distinguish that this is the mobile browser.
(3) What tests should we start with in CI? I am thinking we should land this with amazon and youtube tests running in the general perf-testing cron task. We can increase the tests afterwards.
This sounds like a reasonable place to start.