Epic Agrees: Being Generic Is a Non-Goal

“Being completely generic is a non-goal for Horde.”

That’s not a tweet. Not a hot take. It’s from the official Horde documentation — under a section Epic Games labeled “Opinionated.” The company that builds Unreal Engine, describing how they build Unreal Engine.

They tried generic CI. They stopped, built Horde, and wrote down why. Their FAQ is even more direct: “Most build automation systems are purposefully generic, so you can run any workload on them. That leaves a lot of plumbing for build ops teams to do.”

That’s Epic naming the cost of generic CI. Not speculating. Reflecting on their own experience before Horde — and explaining why they committed hundreds of build agents to a different approach.

Here’s the part nobody talks about.

Roughly half of all Unreal Engine studios still use Jenkins. The company that built the engine said “generic is a non-goal” — and the community heard it, nodded, and set up Jenkins anyway.

I don’t think that’s stupidity. It’s inertia. Jenkins is familiar. Somebody set it up two years ago. There are custom scripts nobody wants to touch. Horde, meanwhile, requires Perforce, takes a week to stand up, and has sparse documentation. So studios acknowledge the philosophy and keep the duct tape.

This isn’t about Horde.

Horde is one implementation. Most studios can’t adopt it. The principle is what survives. If the people who built the engine — who run several hundred EC2 agents on this thing, who ship Fortnite with it — concluded that generic CI is the wrong approach for game builds, that conclusion doesn’t require Horde to be true.

It just requires you to look at your own pipeline and ask whether you chose it, or whether it chose you.

Epic labeled the section “Opinionated.” They weren’t asking you to read between the lines. They put it right there.