[FOLIO-3434] Update NodeJS to Active LTS (v16) in Jenkins images Created: 28/Feb/22  Updated: 05/May/23  Resolved: 17/May/22

Status: Closed
Project: FOLIO
Components: Continuous Integration
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Zak Burke Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File folio-3434-ui-finance-jenkins.txt     Text File folio-3434-ui-orders-jenkins.txt     Text File folio-3434-ui-organizations-jenkins.txt    
Issue links:
Blocks
is blocked by FOLIO-3494 Create new jenkins docker image for N... Closed
Cloners
clones FOLIO-3432 Update NodeJS to Active LTS (v16) in ... Closed
Relates
relates to FOLIO-3433 provide Dockerfile-ish access to GitH... Open
relates to FOLIO-3324 Pin to node 14 for release builds Closed
relates to FOLIO-3511 Verify node v16 build with a Jenkins-... Closed
relates to FOLIO-3324 Pin to node 14 for release builds Closed
Sprint: DevOps Sprint 137, DevOps Sprint 138, Kitfox: sprint 165
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

Summary: Use NodeJS's Active LTS (v16 as of February 2022) in Jenkins CI images for UI repos.

Details: Update the NodeJS version to Active LTS (v16) for the UI repos that remain on Jenkins. (Given the migration from Jenkins to GitHub Actions is underway, I accept that this could be closed as "Won't do" because it's not worth the effort. That's OK if the timeline is short, but it would be helpful to know what that timeline is if so.)



 Comments   
Comment by David Crossley [ 05/May/22 ]

I have built the test image "java-11-test" and followed the usual procedure to verify with various jenkins builds.

Some failed during their "tests" stage.

Okay: folio-snapshot-test build log
Okay: ui-courses build log
Okay: ui-organizations build log
Fail: ui-finance build log
Fail: ui-orders build log

There is an open branch at each: FOLIO-3434-jenkins-docker

I was combining this ticket with the general upgrade of base tools FOLIO-3464 Closed , but got these troubles, so separated. If relevant, that active 2.9.5 image has these supporting tech versions.

This java-11-test image has: node v16.15.0

There are over 50 front-end projects still using Jenkins.

Comment by David Crossley [ 06/May/22 ]

I put this ticket into Blocked state. Will discuss at next DevOps meeting.

 

Comment by Jakub Skoczen [ 09/May/22 ]

Zak Burke Please see David's comment above as some modules break when the image uses v16. I think we should block the devops ticket on an epic to port test and verify that the modules work with v16 before this ticket is closed. Can you please discuss this ticket with the StripesForce team?

Comment by David Crossley [ 09/May/22 ]

We added FOLIO-3494 Closed to provide a mechanism for NPM-based projects to specify a new Jenkins image that has Node v16, or the old one with Node v14.

Comment by Zak Burke [ 09/May/22 ]

Thanks for looping me in, Jakub Skoczen. I'll take a look at those failed build logs and will discuss this with stripes-force (Attn: Khalilah Gambrell). Marching our node versions forward is required work so I think blocking this while we evaluate the build failures, rather than allowing some modules to continue building on older releases, is the best way forward. If the necessary updates turn out to be time consuming then we consider official support for legacy versions, but even so, only for a limited time while we wait for that update work to happen.

Comment by David Crossley [ 10/May/22 ]

I need to move on to utilise that jenkins java-11-test image for another task. I have attached the jenkins logs for those UI modules.

 

Comment by David Crossley [ 17/May/22 ]

This is now ready (done via FOLIO-3494 Closed and FOLIO-3478 Closed ).

The back-end modules, and the remaining front-end Jenkins-based modules, can now utilise either buildNode 'jenkins-agent-java17' (which has Java 17 and Node.js 16) or the default 'jenkins-agent-java11' (which has Java 11 and Node.js 14).

Refer to documentation at:

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