For the jsduck test pipeline, I've already consolidated the jobs and let Zuul trigger it with different project/branch/commit contexts.
rCICFddd8d0e97b50: Consolidate '{name}-jsduck' jobs
For the publish jobs, however, we still have separate ones.
Let's consolidate these as well and add an additional path variable in addition to doc_subpath for the parent directory (e.g. doc_projectpath).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T60772 common gating job for mediawiki core and extensions | |||
| Resolved | hashar | 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 | |||
| Resolved | Krinkle | T91996 Consolidate jobs to test entry points | |||
| Resolved | hashar | T91997 Replace project-specific "{name}-thing" jobs with generic "thing" ones | |||
| Resolved | Krinkle | T91854 Migrate jsduck-publish to use a single job and variable destination path |