This question was created in reference to: [Horde Build Automation and [Content removed]
The referenced questions contains this text
The *stream.json itself can pass this to your BuildGraph script via the "Arguments" property in the template definitionIt does not appear that there is an Arguments property built in. I can see that some sample build graphs do have an Arguments <option> that is subsequently passed to all compile nodes. Is that what the above line refers to? Or is there a way to apply the UBA parameters at the build graph level
I tried adding a “-UBA” entry in the “arguments” array in the steam.json but the arg was not recognized
I also tried adding “-set:Arguments=-UBA”, but it only worked if I modified my build graph to have support for that option.
Just wanted to con
Hey there!
Thanks for the question - specifically this was referring to the arguments template ref parameter.
So a concrete example of this, would be as follows:
// Stream.json "templates": [ { "id": "incremental-build", "name": "Incremental Build", "arguments": [ "-Target=Incremental Build", "-Script=Engine/Build/Graph/Examples/BuildEditorAndTools.xml", "-set:EditorCompileArgs=-UBA -UBALinkRemote", "-set:ExtraToolCompileArguments=-UBA -UBALinkRemote", ] } ]Which as a result would be passed to BuildEditorAndTools.xml:
`
`Let me know if that clarifies the relationship between the stream.json's Template arguments property, and how it's passed into the buildgraph (for subsequent consumption).
Kind regards,
Julian
Yep! That confirms what I was asking! So we need to make sure our build graph passes an Arguments list to every compile node. Some of the examples have this (like BuildAndTestProject.xml), but some don’t (like PresubmitTests.xml)