即使在github.com中断期间，存储库管理器还是缓存启用ember / npm / bower？ [英] Can a repository manager or cache enable ember/npm/bower builds even during github.com outage?
问题描述
我们如何将我们的版本与相当罕见的github.com中断隔离？
How can we insulate our builds against, the pretty rare, github.com outages?
我们使用maven，frontend-maven-plugin + sonatype-nexus v3。 x创建私有缓存，从而将我们的构建与在主要npm存储库中或通过保护程序依赖关系进行的中断或修改隔离（我们在nexus上缓存这些）。
We use maven, frontend-maven-plugin + sonatype-nexus v3.x to create private caches thus insulating our build from outages or modifications made on the main npm repository or via bower dependencies (we cache those too on nexus)
status.github。 com报道了一个中断，我们看到我们的版本开始失败。
status.github.com reported an outage and we saw our builds begin failing.
通过使用nexus repos和shrinkwrap，我们绝大多数外部问题，但不是这一个。
By using nexus repos and shrinkwrap we insulated ourselves from the majority of external problems, but not this one.
如果您有任何想法，请告知我。
Let me know if you have any ideas.
错误
225632 verbose gentlyRm don't care about contents; nuking ./src/frontend/node_modules/.bin/ember
225633 info install ember-cli@2.4.3
225634 info postinstall ember-cli@2.4.3
225635 verbose unlock done using /opt/builds/build-dir/quick-lin-x64-develop/.npm/_locks/ember-cli-387axxxxbbdb3c2.lock for ./src/frontend/node_modules/ember-cli
225636 verbose stack Error: Command failed: git fetch -a origin
225636 verbose stack fatal: remote error:
225636 verbose stack
225636 verbose stack
225636 verbose stack at ChildProcess.exithandler (child_process.js:744:12)
225636 verbose stack at ChildProcess.emit (events.js:110:17)
225636 verbose stack at maybeClose (child_process.js:1008:16)
225636 verbose stack at Socket.<anonymous> (child_process.js:1176:11)
225636 verbose stack at Socket.emit (events.js:107:17)
225636 verbose stack at Pipe.close (net.js:476:12)
[ERROR] npm ERR! argv "src/frontend/node/node" "src/frontend/node/node_modules/npm/bin/npm-cli.js" "install" "--force"
[ERROR] npm ERR! node v0.12.1
[ERROR] npm ERR! npm v2.14.12
[ERROR] npm ERR! code 128
[ERROR]
[ERROR] npm ERR! Command failed: git fetch -a origin
[ERROR] npm ERR! fatal: remote error:
[ERROR] npm ERR!
[ERROR] npm ERR!
[ERROR] npm ERR!
[ERROR] npm ERR! If you need help, you may report this error at:
[ERROR] npm ERR! <https://github.com/npm/npm/issues>
推荐答案
这总是一个有趣的。您可以阅读本文中关于此问题的Sonatype文章，以及如何解决这个问题： https://support.sonatype.com/hc/en-us/articles/ 213465048-Why-does-npm-client-need-access-to-URL-other-than-my-private-registry-
This is always a fun one. You might read this article we've put together over at Sonatype about this issue, and how to workaround it: https://support.sonatype.com/hc/en-us/articles/213465048-Why-does-npm-client-need-access-to-URLs-other-than-my-private-registry-
我是不确定哪个包是导致这个（我看了看ember-cli，它没有立即跳出来）。代码中的某些依赖项可能引用了github URL。我会看看它是什么，并从那里使用我链接的参考文章，了解有关解决问题的信息。希望这有帮助！
I'm unsure which package is causing this (I took a look at ember-cli and it didn't immediately jump out to me). Some dependency somewhere in your code likely has a reference to a github URL. I would look to see which it is, and go from there using the reference article I linked for information on working around the issue. Hope this helps!
这篇关于即使在github.com中断期间，存储库管理器还是缓存启用ember / npm / bower？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
