3 ms·
On the other hand, I have yet to work with, or even meet a developer who thinks that DevOps isn't dumping .tar files or Docker images directly into production.
by Annatar 11y ago
On the other hand, I have yet to work with, or even meet a developer who thinks that DevOps isn't dumping .tar files or Docker images directly into production. The developers love it because it gives them carte blache to just hack production any way they see fit. For instance, I had some Java developer attempt to argue with me that .tar files are the same as .rpm's, and that was just one of many incidents. The worst part is, the developers actively spread that propaganda, along with OS packaging requiring root privileges to deploy payload as being unsuitable for continuous delivery.
- spajus 11y agoI think this is solvable by educating devs, not just by enforcing policies. And path to production should be a well defined process, that has to evolve from collaboration between devs and ops, so nobody should be able to just "hack production" on their own, and ops could also be doing dev code reviews to see what exactly they are doing.
- acdha 11y agoEducation is critical, along with ownership. A lot of the bad practices on either side happen when someone can just fob a mess off onto the other group rather than trying to fix it. Once they have that responsibility it's easier to get someone to care about e.g. how a tarball doesn't address dependency management.