Jenkins is one of those things you configure and forget about...until you need to do it again. Over time, there's so much stuff that it does that replacing it

Jenkins is one of those things you configure and forget about...until you need to do it again. Over time, there's so much stuff that it does that replacing it is a ton of work. And by work I mean verification and communication. Many developers have no idea how stuff gets built, or how dependencies are managed in the build system. You forget one thing and the build is toast. Hunting this info down takes a ridiculous amount of time. Now expand that to X number of projects, and you're looking at a year of work...and a delay while QA checks everything again. For what? Good luck getting that prioritized.