Thanks a lot again! I don’t know how I missed that… I am looking into it and the path is a bit funky.
We have a node which produces tagged files which should be uploaded to Horde as artifacts. Right below the node, outside any node, we do
<Artifact Name="$(ClientTarget)-$(ClientPlatform)-$(TargetConfiguration)-Symbols" Type="symbols" BasePath="$(ArchivedClientBuildDir)" Tag="#$(ClientTarget) $(ClientPlatform) $(TargetConfiguration) Symbols"/>It is outside any node because Artifact is not allowed to exist within a node (based on the Scheme). Setup step of Horde is running on a different machine, which has workspace on different drive letter. I believe that because Artifact is not in node, its $(ArchivedClientBuildDir) is evaluated on this setup machine with different drive letter what leads to path having D:/ instead of E:/ at the beginning.
This looks like a result of mixing UE 5.4 BuildGraph scripts with Horde 5.5. I see that newer scripts use CreateArtifact tasks which can actually be placed inside a node. I will modify it and see if it is resolved.