[FOLIO-3888] investigate broken daily folio-snapshot 20230903 cosmiconfig node18 Created: 03/Sep/23  Updated: 04/Sep/23  Resolved: 04/Sep/23

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

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

Issue links:
Relates
relates to FOLIO-3889 Use Node.js v18 for folio-snapshot re... Closed
Sprint: DevOps Requests
Development Team: None
RCA Group: TBD

 Description   

The folio-snapshot build is broken today 2023-09-03

RUNNING HANDLER [stripes-build : Build stripes] ********************************
FATAL: command execution failed
...
fatal: [10.36.1.143]: FAILED! => {"changed": true, "cmd": "npm_config_global=false
npm_config_unsafe_perm=true npm_config_allow_root=true yarn install",
"delta": "0:00:25.993435", "end": "2023-09-03 01:32:34.216349",
"msg": "non-zero return code", "rc": 1, "start": "2023-09-03 01:32:08.222914",
"stderr": "error cosmiconfig@8.3.2: The engine \"node\" is incompatible with this module. Expected version \">=18\". Got \"16.20.2\"

The cosmiconfig@8.3.2 release today had this change:
set node version to upcoming maintenance LTS.

The folio-snapshot-2 build has been disabled to preserve its build from yesterday.

 



 Comments   
Comment by David Crossley [ 04/Sep/23 ]

The cosmiconfig reverted that with v8.3.3
https://github.com/cosmiconfig/cosmiconfig/issues/320

So now the folio-snapshot build is successful.

Comment by David Crossley [ 04/Sep/23 ]

Followed-on with FOLIO-3889 Closed to upgrade to the Jenkins configuration to generally use Node.js v18 for the reference environments.

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