在cloudbees jenkins上安装Npm失败

有一个奇怪的校验和错误，我不知道出了什么问题。 当我按照cloudbees支持建议安装Npm和node时，以及当我使用node js jenkins插件时，都会发生这种情况。使用-g和不使用-g标志时。怎么了

获取此日志：

> 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

---

有什么线索吗？建议？

问题出现在我称之为“devel”0.11.7的node.js版本和cloudbees fedora linux版本之间。恢复到node.js稳定版本可以解决这一问题，还有其他一些问题