Thanks for your response.
Can you speak to the last 2 bullets please.
- Are autoSDK folders nuked on non incremental builds and pulled fresh?
- If so, how do you handle tooling that should be installed once, but not deleted or messed with later? For example steamcmd.exe, the command line tool to push builds to steam. You can’t be nuking the steamcmd folder all the time, or you will have to redo your steam guard authentication.
A good example of this is steamcmd.exe, the tool used to upload builds to steam. It’s important that the folder structure not be wiped/reset, or you will need to reauthenticate the agent with a steam guard code. So I’m just trying to understand the best approach to implementing this under the build system.
I know I can install steamcmd completely independently and invoke it from the path or something, but I would prefer to do it in a way that doesn’t burden each new agent rollout with custom preparation. I have an autosdk set up with horde already, I am just unclear as to the lifetime guarantees of the data there.
I suppose I could use a setup.bat from the steamcmd autosdk to manage my own “if not exist, install to another folder, out of band with horde/agent delete/repull operations”, but I wanted to ask if there is a better approach before I take that route.