Started by user admin Running as SYSTEM Building in workspace D:\jenkins\workspace\damDance-fvue The recommended git tool is: NONE using credential acb71845-9146-47b3-a91f-6f1885a5272e > D:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > D:\Program Files\Git\bin\git.exe config remote.origin.url http://192.168.30.152:6090/artfess/gcwyjs_web.git # timeout=10 Fetching upstream changes from http://192.168.30.152:6090/artfess/gcwyjs_web.git > D:\Program Files\Git\bin\git.exe --version # timeout=10 > git --version # 'git version 2.24.1.windows.2' using GIT_ASKPASS to set credentials > D:\Program Files\Git\bin\git.exe fetch --tags --force --progress -- http://192.168.30.152:6090/artfess/gcwyjs_web.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > D:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/dev^{commit}" # timeout=10 Checking out Revision f77b35f54d546e014e81c9bdb2fa3c1310592099 (refs/remotes/origin/dev) > D:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10 > D:\Program Files\Git\bin\git.exe checkout -f f77b35f54d546e014e81c9bdb2fa3c1310592099 # timeout=10 Commit message: "待办处置路由" > D:\Program Files\Git\bin\git.exe rev-list --no-walk f77b35f54d546e014e81c9bdb2fa3c1310592099 # timeout=10 [damDance-fvue] $ cmd /c call D:\apache-tomcat-9.0.8\temp\jenkins8148552903423895439.bat D:\jenkins\workspace\damDance-fvue>node -v v12.19.0 D:\jenkins\workspace\damDance-fvue>npm -v 6.14.8 [damDance-fvue] $ cmd /c call D:\apache-tomcat-9.0.8\temp\jenkins3438488291526304972.bat D:\jenkins\workspace\damDance-fvue>npm config set registry https://registry.npm.taobao.org [damDance-fvue] $ cmd /c call D:\apache-tomcat-9.0.8\temp\jenkins8074817319091446319.bat D:\jenkins\workspace\damDance-fvue>npm config get registry https://registry.npm.taobao.org/ [damDance-fvue] $ cmd /c call D:\apache-tomcat-9.0.8\temp\jenkins5647073126134585312.bat D:\jenkins\workspace\damDance-fvue>cd D:\jenkins\workspace\damDance-fvue && npm install && npm run build npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it! npm WARN @wangeditor/editor-for-vue@1.0.0 requires a peer of @wangeditor/editor@>=5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @wangeditor/editor-for-vue@1.0.0 requires a peer of vue@^2.6.14 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\watchpack\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.1 (node_modules\quill-image-resize-module\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) up to date in 37.741s 67 packages are looking for funding run `npm fund` for details > gcwyjs_web@0.1.0 build D:\jenkins\workspace\damDance-fvue > vue-cli-service build postcss-px-to-viewport: postcss.plugin was deprecated. Migration guide: https://evilmartians.com/chronicles/postcss-8-plugin-migration - Building for production... ERROR Error: EBUSY: resource busy or locked, rmdir 'D:\jenkins\workspace\damDance-fvue\dist' Error: EBUSY: resource busy or locked, rmdir 'D:\jenkins\workspace\damDance-fvue\dist' npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! gcwyjs_web@0.1.0 build: `vue-cli-service build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the gcwyjs_web@0.1.0 build 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! C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2023-10-11T06_57_23_641Z-debug.log Build step 'Execute Windows batch command' marked build as failure SSH: Current build result is [FAILURE], not going to run. Finished: FAILURE