3 ms·
Best way is to have CI/CD systems only connected to the official internal repos. Devs can add whatever they feel like on their workstations but it will be a sa
by pjmlp 2y ago
Best way is to have CI/CD systems only connected to the official internal repos.
Devs can add whatever they feel like on their workstations but it will be a sad build server if they get pushed without permission.
- dsr_ 2y agos/Best way/The only safe way/ Anything else will get abused in the name of expediency and just-this-one-time. Also, the process for adding a crate/gem/module/library needs to be the same as anything else: license review, code review, subscription to the appropriate mailing list or other announce channel, and assignment of responsibility. All of these except code review can be really, really fast once you have the process going. All problems are, at least in part, dependency chain management problems.
- sunrunner 2y agoI agree that some amount of friction when including third party dependencies is a vital thing to push people to consider the value versus cost of dependencies (and license review, code review, channel subscriptions are all incredibily important and almost always overlooked), however how should this work for transitive dependendencies? And the dependencies of _those_ dependencies? The dependency trees for most interpreted or source-distributed languages are ridiculous, and review of even a few of those seems practically impossible in a lot of development environments.
- dsr_ 2y agoYou understand the problem clearly, but you haven't put your finger on the solution. It's an obvious one, but distasteful to many people.
- shwouchk 2y agoPerhaps the distaste is blinding me. Would you care to state the obvious very clearly, for the dense ones among us?
- dsr_ 2y ago"The dependency trees for most interpreted or source-distributed languages are ridiculous," Therefore, you must only use software for which the dependency trees are not ridiculous. And that means giving up on software with ridiculous dependencies.
- MeetingsBrowser 2y ago> Devs can add whatever they feel like on their workstations A compromised dev machine is also a problem.
- pjmlp 2y agoTrue, hence we can go next level and also deal with limited accounts for developers, and I can tell you most folks on HN would hate to work in such corporate environments.
- EasyMark 2y agoI'd leave. If I have to beg IT security every other day for something,it's just not worth it. I was in that situation once before and it was endlessly frustrating. It also wasn't even their choice, the CEO dictated it after attending some security talk once upon a time, and then instantly "you can't trust anyone or anything". You can trust my stay there will be short though :)
- pjmlp 2y agoNo doubt, although this is always a job market situation, in many places around the globe being a developer isn't much different from any other office job, where many folks have to be happy to have a job in first place.