Quote of mail, that went to prod-dept mailing list:
Hi All, Sorry for casting such a wide net, however time is of the essence. Currently we are potentially at risk with upstream, node.js / npm registry. There is excess traffic from Red Hat, we are potentially violating our terms of use. They have reached out to us and asked us to take action. To help limit the amount of traffic. This issues is already being worked on at several levels inside of Red Hat. This email is not to explore any more solutions at this time. This email is a request to Red Hat engineering to use our internal local registry / cache [1] for getting npm dependencies. *Disclosure I am not a node.js / npm expert. Some specific details on what is needed in your specific configurations to ensure you are using the internal registry I may not have, but I will help where I can. If you have questions please reach out to me (off-list) preference would email or google chat. [1] https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org Thank you in advance, Jeff
We should make sure all our (npm based) jobs are using our internal npm package mirror.
- relates to
-
CRW-360 Use internal npm registry for CRW builds / switch to cachito
-
- Closed
-
- links to