- CI images
- Quibble images
- Node images
- MW-Vagrant
-
LibUp
Description
Details
Event Timeline
In general, jsduck is triggered via the CI job template extension-javascript-documentation which isn't defined for release branches, and e.g. its sub-job mwext-node18-docs-publish only runs for the master branch – so, once we've finally eliminated it from all master branches (still a work in progress!) this should suffice.
As part of the Continuous-Integration-Infrastructure (Zuul upgrade) we are overhauling all jobs and support for jsduck will be removed entirely. I expect the migration to happen after the summer of 2025.
Change #1342045 had a related patch set uploaded (by Jforrester; author: Jforrester):
[integration/config@master] Docker: [quibble-bookworm, node24-test, node26-test] Drop jsduck and Ruby supports
Change #1342045 merged by jenkins-bot:
[integration/config@master] Docker: [quibble-bookworm, node24-test, node26-test] Drop jsduck etc.
Mentioned in SAL (#wikimedia-releng) [2026-09-15T20:46:42Z] <James_F> Docker: [quibble-bookworm, node24-test, node26-test] Drop jsduck etc. for T363905
Change #1342051 had a related patch set uploaded (by Jforrester; author: Jforrester):
[integration/config@master] jjb: Update node and Quibble jobs for the jsduck removal
Change #1342051 merged by jenkins-bot:
[integration/config@master] jjb: Update node and Quibble jobs for the jsduck removal
Let's call this done, and the Vagrant concern can be removed if/when someone cares there.