3 ms·
Best practice is to have a local repo that caches every package your code depends on. See https://en.wikipedia.org/wiki/Software_repository#On-Premise_Products_
by Someone 6y ago
Best practice is to have a local repo that caches every package your code depends on. See https://en.wikipedia.org/wiki/Software_repository#On-Premise_Products_providing_repository_management https://en.wikipedia.org/wiki/Software_repository#On-Premise... for tools.
Your code then should resolve all its dependencies through that cache. If the cache doesn’t have it yet it goes to the real repo to resolve it. Then, it gives you its copy.
You typically can also use these products to store/archive any binaries you produce.
I don’t know how well these work if, as you say, you want to automatically pull future commits. That feels like a dangerous practice to me.
- gervwyk 6y agoThanks. Yes, just meant keeping a local copy of the repo from a maintenance / future proof perspective, but obviously still curate next versions before including into build.