Page MenuHomePhabricator

Uninstall jsduck and related material from CI images etc., once it's no longer needed
Closed, ResolvedPublic

Description

Search

  • CI images
    • Quibble images
    • Node images
  • MW-Vagrant
  • LibUp

Related Objects

StatusSubtypeAssignedTask
ResolvedJdforrester-WMF
Resolvedapaskulin
Resolved• Jhernandez
DuplicateNone
ResolvedKrinkle
Resolvedapaskulin
OpenNone
ResolvedEsanders
ResolvedEsanders
ResolvedBUG REPORTKrinkle
ResolvedJdlrobson
DuplicateNone
DuplicateNone
DuplicateNone
Resolved• nray
ResolvedJdforrester-WMF
Resolved• matmarex
DeclinedNone
Resolvedcscott
ResolvedTheDJ
Resolved• Samwilson
ResolvedNone
OpenNone
DeclinedNone
Resolvedapaskulin
ResolvedKrinkle
Resolved• matmarex
Resolvedapaskulin
DeclinedBUG REPORTJdlrobson
Resolvedapaskulin
Resolvedegardner
OpenNone
OpenNone
OpenNone
ResolvedNovem_Linguae
ResolvedNovem_Linguae
ResolvedNovem_Linguae
Resolvedsanthosh
OpenNone
DuplicateNone
OpenNone
OpenNone

Event Timeline

Jdforrester-WMF renamed this task from Uninstall jsduck and related material from CI images, once it's no longer needed to Uninstall jsduck and related material from CI images etc., once it's no longer needed.May 1 2024, 10:51 AM
Jdforrester-WMF updated the task description. (Show Details)

How do we deal with jsduck still being used in the release branches?

How do we deal with jsduck still being used in the release branches?

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.

taavi updated the task description. (Show Details)

Note: Even though T138401 has been marked Resolved, it's not yet done. There are a bunch of production repos that still need to migrate — Wikispeech (T379691), ArticleCreationWorkflow (T379692), and DonationInterface (T379693) — before we can drop the support from CI. :-(

Novem_Linguae changed the task status from Open to Stalled.Nov 13 2024, 2:57 PM

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

https://gerrit.wikimedia.org/r/1342045

Change #1342045 merged by jenkins-bot:

[integration/config@master] Docker: [quibble-bookworm, node24-test, node26-test] Drop jsduck etc.

https://gerrit.wikimedia.org/r/1342045

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

https://gerrit.wikimedia.org/r/1342051

Change #1342051 merged by jenkins-bot:

[integration/config@master] jjb: Update node and Quibble jobs for the jsduck removal

https://gerrit.wikimedia.org/r/1342051

Jdforrester-WMF claimed this task.

Let's call this done, and the Vagrant concern can be removed if/when someone cares there.