4 ms·
>- ci/cd is maybe not relevant to your users, but its about your own sanity, it forces complete documentation in code of what is done to build and ship, decoupl
by rjbwork 6y ago
>- ci/cd is maybe not relevant to your users, but its about your own sanity, it forces complete documentation in code of what is done to build and ship, decouple it from local dev setups and make as deterministic as possible. Even small project benefit, have you ever come back after 2 years and took hours to remember the order of voodoo commands or lost a laptop and then had to install specific versions of cli tools?
This to me is the biggest advantage of this sort of thing. Documentation and notes are great, but I'd rather just have the thing-in-itself available that does the job.
- jFriedensreich 6y agoYeah and 13 years ago there was a similar argument about git. I heard a lot of developers say well its a small project and its just me, no way i'm dealing with repos, making commits and learn git or mercurial. This completely died out.
- Person5478 6y agoCI/CD doesn't require the cloud or containers.
- megous 6y agoI can go back to projects I wrote 10-14 years ago, and the same build/deploy scripts still work today. I used standard POSIXy or GNU tools back then. They still work the same way today. It really depends on how you pick what you depend on. Would some random third party CI/CD infrastructure, I might have selected 10 years ago still work or be in business today? Hard to say. Maybe I would have picked something that stayed supported until this day, maybe not...