[chrismarlow9]

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]

It'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.

[pgeorgi]

A 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/...

[chrismarlow9]

This is the route I take in my personal projects. Jenkins runs a make file.

[hawski]

I 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.