Page MenuHomePhabricator

Uninstall jsduck and related material from CI images etc., once it's no longer needed
Open, Needs TriagePublic

Description

Search

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

Related Objects

StatusSubtypeAssignedTask
OpenNone
Openapaskulin
Resolved Jhernandez
DuplicateNone
ResolvedKrinkle
Resolvedapaskulin
OpenNone
ResolvedEsanders
ResolvedEsanders
ResolvedBUG REPORTKrinkle
ResolvedJdlrobson
DuplicateNone
DuplicateNone
DuplicateNone
Resolved nray
ResolvedJdforrester-WMF
Resolvedmatmarex
DeclinedNone
Resolvedcscott
ResolvedTheDJ
ResolvedSamwilson
ResolvedNone
OpenNone
DeclinedNone
Resolvedapaskulin
ResolvedKrinkle
Resolvedmatmarex
Resolvedapaskulin
DeclinedBUG REPORTJdlrobson
Resolvedapaskulin
Openegardner
OpenNone
OpenNone
OpenNovem_Linguae
ResolvedNovem_Linguae
OpenNovem_Linguae

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)