Most build processes (from basic scripts or Makefiles all the way up to CI/CD product-specific pipeline configurations) are complex, brittle, opaque and poorly understood by most of the team. I've seen time and time again one or two people emerge as the "build" people because most team members want to run as far away as they can, and it's easier to let someone else gatekeep the mysterious black box that sometimes does something useful. These processes typically grow organically on an as-needed basis and are rarely designed under a unifying vision.
I think it's a combination of lack of experience on the engineers part, bad off the shelf tooling, lack of recognition of the cost and as a result under investment by the business.
If you're using any one of the popular suites (github, travis, circle), you should be able to fork your own little CI fiefdom insulated from the depredations of the incompetent.
One team member in particular is talking about it constantly.
You have to understand only a small fraction of the tech workforce makes a living off code. The rest of us have to do it by talking.
Then again, nearly all answers on Ask HN are rebuffed by the the poser, so Ask HN is really more akin to craigslist's "rants and raves" or reddit's /r/amianasshole.