5 ms·
> Don't build your CI/CD pipelines; use Vercel or something similar I'd give exactly the opposite advice. Being able to properly debug your CI/CD code, or even
by drowsspa 3y ago
> Don't build your CI/CD pipelines; use Vercel or something similar
I'd give exactly the opposite advice. Being able to properly debug your CI/CD code, or even run locally, has been a godsend when you're starting up.
- JonChesterfield 3y agoI haven't met vercel. Hudson, buildbot, in house thing built from scratch for some reason - all bad associations here. A CI / deployment pipeline that you can't run locally is absolutely a disaster. You end up building different code to prod, in different fashion, and generally hoping that bugfixes to the local one will be meaningful in the CI one. Buildbot calling a top level makefile that does everything, fine. Some java thing that is configured through a web gui and thus can never be restarted if it ever disappears, not fine. I love the idea of CI and loathe every instance I have ever used.
- gpjanik 3y agoI agree with you, however modern services (like Vercel) solve those problems pretty well. They provide you with the CI you'd otherwise write by yourself.
- gpjanik 3y agoThere should be no CI/CD code - build the product instead. Fundamentally, outsource devops to some service. Use Firebase, Vercel, etc. Building proper multi-environment CI/CD is where you're doing devops with the belief you're going to be "better at it" with "more control", eventually writing code nobody asked you for.