1563708 - [meta] Migrate CI from Chromium to Chrome

Status: RESOLVED FIXED

(Testing :: Raptor, task, P1)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

This meta bug tracks migrating from Chromium to Chrome for all Raptor tests running in CI.

Comment 1

[Dave Hunt [:davehunt] [he/him] ⌚BST]

In bug 1528731 we had originally planned to migrate to a pre-release of Chrome such as Canary, Dev, or Beta. We have since determined that Canary is much slower and not a suitable comparison point for us. We also identified several challenges to updating these channels on a frequent (daily) schedule. We're now considering targeting Chrome release, which currently updates every 6 weeks.

:fubar do the challenges discussed in bug 1528731 still apply if we target Chrome release instead of Canary/Dev? What kind of effort would be involved in provisioning Chrome release automatically on our target platforms (mac, win, linux)? Would there be an option for making Chrome release available in CI, but having the update process performed manually every 6 weeks?

Comment 2

[Kendall Libby [:fubar] (he/him)]

(In reply to Dave Hunt [:davehunt] [he/him] ⌚️UTC from comment #1)

:fubar do the challenges discussed in bug 1528731 still apply if we target Chrome release instead of Canary/Dev? What kind of effort would be involved in provisioning Chrome release automatically on our target platforms (mac, win, linux)? Would there be an option for making Chrome release available in CI, but having the update process performed manually every 6 weeks?

I think we're ok to go ahead and give it a go.

On Linux Chrome depends on the normal OS update procedure so we can install it and update it at our own leisure. On macOS it's a simple dmg and auto-update appears to not be enabled by default, so a similar situation. I need a little more info on the Windows side, but if there's an update service it should be easy enough to disable it. So this should be easy enough to do on the hardware systems. Updating will be manual, as we'll have to update our puppet configs.

There's also a second option but it puts more work onto your team; it's also our fall back if something in the above goes terribly sideways. This would be to upload the various Chrome packages to tooltool and then have the test scripts/harness install it into the task user space instead of system-wide. This will be easier when user separation is done across the board, so it's Plan B at the moment.

Comment 3

[Dave Hunt [:davehunt] [he/him] ⌚BST]

I don't think we should block this on bug 1583846, and believe therefore this can be resolved.