Change Details

I think we'll need to do the following: 1. [[https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/508692|Temporarily disable selenium jobs in core]] 2. Temporarily remove webdriverio from core's and any gated extension's npm build (as it's node10-incompatible) 3. Upgrade the docker base image to node10 4. Fix resulting non-selenium gate issues we discover, like MobileFrontend hard-coding checking 6.11.0 5. {T213268} (in core and elsewhere in gate) and re-enable 6. Migrate selenium jobs to new format 7. Re-enable selenium jobs in core 8. Tell people to look for issues 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?

I think we'll need to do the following: [x] [[https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/508692|Temporarily disable selenium jobs in core]] [x] Temporarily remove webdriverio from core's and any gated extension's npm build (as it's node10-incompatible) [x] 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 [ ] Fix resulting non-selenium gate issues we discover, like MobileFrontend hard-coding checking 6.11.0 [ ] {T213268} (in core and elsewhere in gate) and re-enable [ ] Migrate selenium jobs to new format [ ] Re-enable selenium jobs in core [ ] Tell people to look for issues 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?

I think we'll need to do the following: 1.[x] [[https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/508692|Temporarily disable selenium jobs in core]] 2.[x] Temporarily remove webdriverio from core's and any gated extension's npm build (as it's node10-incompatible) 3.[x] Upgrade thee quibble docker base image to node10 https://gerrit.wikimedia.org/r/c/integration/config/+/514021 4. Fix resulting non-selenium gate issues we discover, like MobileFrontend hard-coding checking 6.11.0[ ] Switch all repos to use the node10-based quibble images https://gerrit.wikimedia.org/r/c/integration/config/+/514034 5.[ ] Fix resulting non-selenium gate issues we discover, {T213268} (in core and elsewhere in gate) and re-enablelike MobileFrontend hard-coding checking 6.11.0 6. Migrate selenium jobs to new format[ ] {T213268} (in core and elsewhere in gate) and re-enable 7. Re-enabl[ ] Migrate selenium jobs in coreto new format 8.[ ] Re-enable selenium jobs in core [ ] Tell people to look for issues 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?