Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

travis-ci should host a local npm mirror for node.js projects #2554

Closed
tjwebb opened this Issue · 4 comments

4 participants

@tjwebb

For the following reasons:
1. it would reduce travis-ci bandwidth usages, lowering costs
2. it would reduce average time needed per test run, increasing VM availability and thus lowering costs and improving user experience.
3. For node.js projects, nondeterministic failure is often due to failures involving network connection to npm registry
4. It's the right thing to do, given that travis-ci is an automated service that increases load on the npm registry.

In sum, I think that the world is a better place with this feature than without it, and I think that Travis CI and its customers would benefit.

@joshk
Owner

Hi Travis,

Thanks for the suggestion.

This is something that we are interested in doing, but we don't have an ETA on this yet sorry.

Regarding point 1, this would not reduce our bandwidth usage or affect costs for us and for users.

And for point 4, has anyone at the npm registry complained about the load we are putting on them?

Have a great day,

Josh

@tjwebb

Regarding point 1, this would not reduce our bandwidth usage or affect costs for us and for users.

Is that because you don't pay for bandwidth? Obviously if you host a mirror on your local network, you'd drastically reduce your transfer between travis-ci and the world.

And for point 4, has anyone at the npm registry complained about the load we are putting on them?

Not that I know of, but their infrastructure is funded mainly from donations. re: "It's the right thing to do"

@avdg

Not a real solution (as it must be done at repo level), but it can speed up builds:

Simply add this to your travis.yml file

sudo: false
cache:
  directories:
    - node_modules

This will use the container-based infrastructure to gain access to the cache feature, this with few restrictions (disallow the use of sudo, setuid and setgid executables)
See here: http://docs.travis-ci.com/user/workers/container-based-infrastructure/.

Although this is a temporal solution, I really would love a solution on infrastructure level. A good solution could speed up builds, save bandwidth, reduce resources and reduce costs without cutting too much in delivering good service (apart from maintaining the cache maybe?).

@roidrage
Owner

I'm closing this issue for now, as we have no immediate plans to add this feature.

Should we add it to the roadmap eventually, we'll make sure to update this ticket.

@roidrage roidrage closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.