|Resolved||hashar||T60772 common gating job for mediawiki core and extensions|
|Open||None||T69216 Have unit tests of all wmf deployed extensions pass when installed together, in both PHP-Zend and HHVM (tracking)|
|Invalid||Ryasmeen||T90647 Create Jenkins builds for Editing across repositories (MobileFrontend, VisualEditor etc)|
|Declined||None||T50407 Jenkins: Setup Vagrant for some jobs (tracking)|
|Declined||None||T45266 Write and implement tests for Wikimedia's Apache configuration (redirects.conf, etc.)|
|Resolved||hashar||T47499 [EPIC] Run CI jobs in disposable VMs|
|Invalid||hashar||T86172 Write a migration plan for CI infra to the disposable VMs infrastructure|
|Resolved||hashar||T86171 Design the Jenkins isolation architecture|
|Declined||hashar||T97472 Create a Trusty labs image for CI isolation project|
I filled that task after some random discussion we had were we envisioned creating a 2nd CI infra (with a 2nd Zuul server).
In the end we only added Nodepool and a dedicated labs project for its instance. The Zuul scheduler has the logic to route jobs the different slaves.
An example is https://gerrit.wikimedia.org/r/#/c/241671/ i.e. a JJB job definition needs:
node: ci-jessie-wikimedia properties: - zeromq-event
And in Zuul:
- name: ^tox-jessie$ parameter-function: offline_when_complete