Wasn't sure where to put this, but noticed it just now:
- mwgate-node10-docker
- wmf-quibble-vendor-mysql-hhvm-docker
- wmf-quibble-vendor-mysql-php72-docker
- wmf-quibble-core-vendor-mysql-hhvm-docker
- wmf-quibble-core-vendor-mysql-php72-docker
- quibble-vendor-mysql-hhvm-docker
- quibble-vendor-mysql-php72-docker
- wmf-quibble-selenium-hhvm-docker
- wmf-quibble-selenium-php72-docker
- mwskin-php72-phan-docker
- mwskin-php72-phan-seccheck-docker
I understand the non-quibble jobs, the quibble-selenium jobs and one "main" quibble job in hhvm+php72.
But there are 3x2 seemingly "main" quibble jobs:
- wmf-quibble-vendor-mysql-{hhvm,php72}-docker
- wmf-quibble-core-vendor-mysql-{hhvm,php72}-docker
- quibble-vendor-mysql-{hhvm,php72}-docker
The first one, "wmf-quibble-vendor-mysql-*" is the one we run on patches against the master branch as well and the one I see most often and is afaik the "extension gate" and "main" quibble job. But what are these other two?
Perhaps one of them is plain mediawiki core without the extension gate, which is normally called "mediawiki-quibble" on the master branch. That makes sense I suppose, although we could consider dropping it (outside scope of this task).
But my questions:
- Is one of these two the plain MW core job, if so which one?
- What is the other one for?