Poppy 2023 R2 - Update Node.js to v18 (FOLIO-3870)

[FOLIO-3871] Update Jenkins CI image to use Node.js v18 Created: 03/Aug/23  Updated: 06/Dec/23  Resolved: 06/Dec/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None
Parent: Poppy 2023 R2 - Update Node.js to v18

Type: Task Priority: P2
Reporter: Zak Burke Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: security, security-reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-3725 Rebuild folioci/jenkins-slave-all for... Closed
relates to FOLIO-3889 Use Node.js v18 for folio-snapshot re... Closed
Sprint: DevOps Requests
Development Team: FOLIO DevOps
Release: Poppy (R2 2023)
Epic Link: Poppy 2023 R2 - Update Node.js to v18
RCA Group: TBD

 Description   

Summary: Update the Jenkins CI image to use Node.js v18 (active LTS) since v16's EOL is 2023-09-11.

Details: When we discussed this on 2023-05-22, it was noted that we currently have images with Java 11/Node.js 14 and Java 17/Node.js 16, but what we really want is a Java 17 image with Node.js 16 and another with Node.js 18. We need to keep a Node.js v16 image around at least as long as Nolana is supported because the UI will not build under v18



 Comments   
Comment by David Crossley [ 18/Aug/23 ]

If i understand correctly, then John Malconian already did this via FOLIO-3725 Closed .

Comment by Khalilah Gambrell [ 06/Dec/23 ]

Hey David Crossley John Malconian Zak Burke  - can we close this issue as a duplicate based on above comment?

Comment by David Crossley [ 06/Dec/23 ]

Yes, closed.

Generated at Thu Feb 08 23:31:24 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.