2013-10-15 202 views
1

有一個奇怪的校驗和錯誤,我無法弄清楚什麼是錯的。 它發生在我安裝Npm和node時,因爲cloudbees支持建議和我使用node-js-jenkins插件。當使用-g而不使用-g標誌時。怎麼了?Npm安裝在cloudbees上失敗jenkins

得到這個日誌:

> Unpacking http://nodejs.org/dist/v0.11.7/node-v0.11.7-linux-x64.tar.gz 
> to 
> /scratch/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node_0.11.7 
> on s-68b3777c $ 
> /scratch/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node_0.11.7/bin/npm 
> install -g grunt-cli phantomjs jshint npm http GET 
> https://registry.npmjs.org/phantomjs npm http GET 
> https://registry.npmjs.org/jshint npm http GET 
> https://registry.npmjs.org/grunt-cli npm http 200 
> https://registry.npmjs.org/grunt-cli npm http GET 
> https://registry.npmjs.org/grunt-cli/-/grunt-cli-0.1.9.tgz npm http 
> 200 https://registry.npmjs.org/jshint npm http 200 
> https://registry.npmjs.org/phantomjs npm http GET 
> https://registry.npmjs.org/jshint/-/jshint-2.1.11.tgz npm http GET 
> https://registry.npmjs.org/phantomjs/-/phantomjs-1.9.2-2.tgz npm http 
> 200 https://registry.npmjs.org/grunt-cli/-/grunt-cli-0.1.9.tgz npm 
> http 200 https://registry.npmjs.org/phantomjs/-/phantomjs-1.9.2-2.tgz 
> npm http 200 https://registry.npmjs.org/jshint/-/jshint-2.1.11.tgz npm 
> ERR! Error: shasum check failed for 
> /home/jenkins/tmp/npm-399-NkLy1zBO/1381868137921-0.8519227004144341/tmp.tgz 
> npm ERR! Expected: eb5108fef9ba5ddebb830983f572d242e49e3f96 npm ERR! 
> Actual: b80f62e5bdfed4297392de2ed8711d5aff5e5742 npm ERR!  at 
> /scratch/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node_0.11.7/lib/node_modules/npm/node_modules/sha/index.js:38:8 
> npm ERR!  at ReadStream.<anonymous> 
> (/scratch/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node_0.11.7/lib/node_modules/npm/node_modules/sha/index.js:85:7) 
> npm ERR!  at ReadStream.EventEmitter.emit (events.js:125:20) npm 
> ERR!  at _stream_readable.js:896:16 npm ERR!  at 
> process._tickCallback (node.js:317:11) npm ERR! If you need help, you 

任何線索?建議?

回答

0

問題轉向我調用的node.js版本('devel'0.11.7)和cloudbees fedora linux版本之間。恢復到node.js 穩定版本排序解決了這個問題(還有其他問題與他們..)