3 ms·
there's no need for this to be an either/or decision. private artifact repos with the ability to act as a caching proxy are easy to set up. afaik all the major
by inhumantsar 2y ago
there's no need for this to be an either/or decision.
private artifact repos with the ability to act as a caching proxy are easy to set up. afaik all the major cloud providers offer basic ones with the ability to use block or allow lists.
going up a level in terms of capabilities, JFrog is miserable to deal with as a vendor but Artifactory is hard to beat when it comes to artifact management.
- jiggawatts 2y agoSure… for like one IDE or one language. Now try that for half a dozen languages, tools, environments, and repos. Make sure to make it all work for build pipelines, and not just the default ones either! You need a bunch of on-prem agents to work around the firewall constraints. This alone can keep multiple FTEs busy permanently. “Easy” is relative. Maybe you work in a place with a thousand devs and infinite VC money protecting a trillion dollars of intellectual property then sure, it’s easy. If you work in a normal enterprise it’s not easy at all.
- junto 2y agoTheir caching proxy sucks though. We had to turn it off because it persistently caused build issues due to its unreliability.