You are not alone wondering this. I find there are less brittle more modern task runners available today, however Jenkins still has a strong hold on traditional

You are not alone wondering this. I find there are less brittle more modern task runners available today, however Jenkins still has a strong hold on traditional enterprise IT systems that struggle with change. My theory is it has to do with the whole traditional break up of responsibilities between dev and operations. As more developers are taking over ops (cough devops cough) they’re quickly replacing Jenkins with systems that align well to what they’re used to (rich CLI support, rich programming support, Unix like) vs. zero programming required plugin based. So it’s not that Jenkins is necessarily bad — it just doesn’t fit in with the new crowd — although I personally think it just sucks in general and can single-handedly destroy modern CI/CD dev culture, but that’s JOPO...