I'm unclear on why this is required right now Tom FENNELLY. I've seen flakey builds before at previous workplaces but I'm not sure where in our project infrastructure this is impacting right now

R. Tyler Croy Workflow CI build has failed on a few occasions due to intermittent connection failures to the NPM registry.

Tom FENNELLY will you link some of those failed builds to this JIRA so I have some concrete problems to weigh the priority of this request with?

Hasn't failed in the recent build history of workflow, so will downgrade the priority of this.

This should be something we can do via repo.jenkins-ci.org relatively easily at some point in the future.

Since that mirror would still be public, it has the potential to have the same availability issues (from the builders' perspective) that the public package mirrors do.

If we do this, I wonder if it could be done such that the mirror is only used for CI server builds i.e. the CI job needs to be configured to use the registry, otherwise the public NPM registry is used (e.g. local dev builds)?

And yeah, like you say, it probably only helps make things more stable if the mirror is local to the CI infra.

We're getting bitten by this again atm ... CI jobs failing.

Hi Tom,

If your builds are on DEV@cloud we are impacted by an issue from NPM : http://status.cloudbees.com/incidents/kg1yzxkgtsnx

Sorry for this.

Arnaud Héritier Thanks Arnaud. Yes, this is the issue I was referring to in the previous comment.

An npm registry should be set up as a caching repo here: https://repo.jenkins-ci.org/api/npm/npm

Please test it out and let me know if there are issues

As far as I can tell, this has been completed. I ran this command npm install azure --registry https://repo.jenkins-ci.org/api/npm/npm and that seemed to work fine.