3 ms·
Just my opinion but make is still the best ci/cd tool. I see way too many places with layers of tools and yaml configs and hosted cvs pipelines (that you can't
by chrismarlow9 3y ago
Just my opinion but make is still the best ci/cd tool. I see way too many places with layers of tools and yaml configs and hosted cvs pipelines (that you can't easily recreate locally), when a make file would do just fine if not better.
- kristjansson 3y agoIt's very, very convenient to have your CI/CD yaml just trigger make targets. Still get the benefits of everything running on Someone Else's Computer, but mostly-to-100% reproducible locally for debugging.
- chrismarlow9 3y agoThis is the route I take in my personal projects. Jenkins runs a make file.
- pgeorgi 3y agoA hard learned lesson we had over at coreboot. Now all the projects we run CI for are heading towards some variant of `make what-jenkins-does` as in https://review.coreboot.org/plugins/gitiles/coreboot/+/refs/heads/master/util/testing/Makefile.inc#93 https://review.coreboot.org/plugins/gitiles/coreboot/+/refs/...
- hawski 3y agoI recently started eyeing ninja and for many cases it makes more sense than make. Still those ci/cd configs should always be very thin wrappers (single command for single thing) around whatever script tooling is used internally.