Currently the gate-and-submit pipeline has a higher priority than the test pipeline. This is a good thing; however, within the gate-and-submit pipeline there are subqueues, but no defined priorities. Certain tests require a faster turn around than others, so we should create a means by which zuul can prioritize the gate-and-submit queue.

The way Zuul work and how we have it configured is:

There is a pipeline gate-and-submit that supports multiple queues and reacts to Code-Review +2 events.

Most projects are registered with that pipeline and projects share the same queue whenever they share the same job. For example mediawiki/core and mediawiki/vendor share the same job mediawiki-extensions-qunit-jessie. Patches are then enqueued in the order they received the CR+2, regardless of the target branch. Doc https://docs.openstack.org/infra/zuul/gating.html

This task is about decoupling MediaWiki patches targeting the wmf/* branches. To work around Zuul not supporting branch we would need a new gate pipeline that would only react to wmf branches. Probably by making the Gerrit trigger to filter events by branch: ^wmf/.