记Jenkins中前端项目发布失败的问题,报错GLIBC_2.16 not found
文章目录
项目在本地运行正常,在Jenkins中编译的时候失败,报错内容:
+ npm run release online
> component-cloud@1.0.0 release /data/jekins/workspace/component-cloud
> node --version && npm --version && npm install && npm run build && npm run pack && echo success "online"
node: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.17' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by node)
node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by node)
node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by node)
node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.19' not found (required by node)
node: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by node)
node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by node)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! component-cloud@1.0.0 release: `node --version && npm --version && npm install && npm run build && npm run pack && echo success "online"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the component-cloud@1.0.0 release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/iotdev/.npm/_logs/2021-01-25T03_02_00_782Z-debug.log
Build step 'Execute shell' marked build as failure
Finished: FAILURE按报错信息,说明Linux系统中的GLIBC版本不正确。网上查了GLIBC,这是Linux的底层API,很多依赖都引用到它,贸然升级或导致其它依赖出现问题。
进入服务器中该项目目录下手动编译项目npm run build,失败,报错内容同上。确定不是Jenkins导致该错误。
想到该项目并未在相关敏感依赖上有变化,推测该报错并非代码导致。
在服务器上新建了一个文件夹,将项目代码克隆到该路径下git clone xxxxxxxxxxxxx.git,执行发布操作npm run release online
发现项目正常发布,得出结论:服务器的相关依赖没有问题。据此推测或为某种缓存导致问题产生。
清空项目目录,重新将项目从仓库克隆至该目录,再次执行编译npm run build,成功。再Jenkins再次进行构建,成功。问题解决。
最后:在项目某个版本的依赖中,用到了node.js,但是后来又移除了对node的依赖,猜测该问题主要原因是高版本node造成的。
评论
登录后参与技术讨论,分享你的经验与见解。
登录 / 注册暂无评论