Horde Build automation path

anonymous-edc · September 22, 2025, 9:25pm

Hello,

I’ve set up a new Horde project for build automation with the following components in place:

Stream configuration
Project JSON setup
Perforce connection

Issue:

While P4 workspace synchronization to the Horde agent works correctly, I’m encountering a path resolution problem during the Setup Build phase. Horde is searching for RunUAT.bat in this default path:

 
C:\HordeAgent\Test\Demo\Sync\Engine\Build\BatchFiles\RunUAT.bat

However, our project structure is different:

P4 Stream: //abc/pr/mainline
Engine location: toto/Engine (where toto is our root folder)
We maintain the standard UnrealEngine folder structure below the toto folder

Required Solution:

How to configure Horde to look for RunUAT.bat at:

C:\HordeAgent\Test\Demo\Sync\toto\Engine\Build\BatchFiles\RunUAT.bat

Question:

How can I modify Horde’s configuration to recognize our custom Engine path structure?

Thank you

JulianGamble · September 29, 2025, 5:23pm

Hey Victor,

Hmm, I think this is going to likely present some substantial problems IMO. If you are comfortable in diverging a part of the horde agent to see how far you get, you can look here:

JobExecutor.cs:

result = await ExecuteCommandAsync(step, workspaceDir, Environment.GetEnvironmentVariable(“COMSPEC”) ?? “cmd.exe”, $“/C \”\"{workspaceDir}\\{EnginePath}\\Build\\BatchFiles\\RunUAT.bat
- https://github.com/EpicGames/UnrealEngine/blob/5\.6/Engine/Source/Programs/Horde/Drivers/JobDriver/Execution/JobExecutor.cs\#L1521

I think a tactical solution here may be to have a new import stream that just synthesizes the two so that your engine is sitting at the appropriate location?

Julian

anonymous-edc · October 1, 2025, 1:51pm

Thank you Julian.

I guess there is no easy way