I think we'll need to do the following:
- Temporarily disable selenium jobs in core
- Temporarily remove webdriverio from core's and any gated extension's npm build (as it's node10-incompatible)
- Upgrade the quibble docker base image to node10 https://gerrit.wikimedia.org/r/c/integration/config/+/514021
- Switch all repos to use the node10-based quibble images https://gerrit.wikimedia.org/r/c/integration/config/+/514034
- Re-enable selenium jobs in core https://gerrit.wikimedia.org/r/c/mediawiki/core/+/514085
- Tell people to look for issues
- Fix resulting non-selenium gate issues we discover, like MobileFrontend hard-coding checking 6.11.0
I think this'll have to happen pretty rapidly to avoid too much bitrot from the selenium tests, as I don't see a way of proceeding without switching selenium off first. Anyone want to volunteer to pair on this?