Note that this will suffice for most repos (MediaWiki, extensions and skins, libraries, etc.), but for things built via the pipeline (services, some libraries, etc.) they need a "real" production image, not a CI image, which means they will have to wait for T284346: Provide a node 12 production image (based on bullseye?).
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| integration/config | master | +223 -0 | dockerfiles: Provide node12* tree based on ci-bullseye |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T284730 selenium-daily-beta-CirrusSearch fails with `Request failed due to invalid argument: invalid argument: unrecognized capability: chromeOptions` | |||
| Resolved | Krinkle | T284696 Update Fresh from Node.js 10 LTS to Node.js 12 LTS | |||
| Resolved | Jdforrester-WMF | T284345 Upgrade all CI jobs for WMF-deployed projects from Node 10 to Node 12 | |||
| Resolved | Jdforrester-WMF | T284343 Create WMF CI image for Node.js 12 |
Event Timeline
Comment Actions
Change 695657 had a related patch set uploaded (by Jforrester; author: Jforrester):
[integration/config@master] dockerfiles: Provide node12* tree based on ci-bullseye
Comment Actions
Change 695657 merged by jenkins-bot:
[integration/config@master] dockerfiles: Provide node12* tree based on ci-bullseye
Comment Actions
Mentioned in SAL (#wikimedia-releng) [2021-06-04T19:19:59Z] <James_F> Docker: Publishing node12 CI images T284343