Possible to automate setup of CryEngine, for continuous integration slaves?

Hi there, first post. I'm setting up some infrastructure for continuous integration, involving a CryEngine game. This'll involve several tens of VMs, quite likely, and so an automated build process for a golden image for those VMs is key to a stable and predictable build environment. For the curious, I'm using https://packer.io for the AWS & GCE image creation, https://www.ansible.com for the machine configuration, and some https://goss.rocks for some automated testing (where I'll probably upstream bits of Windows support that I need).

I'd like to find out if it's possible to automate the setup of the CryEngine. I've downloaded the launcher, ce-launcher.exe, but so far have not discovered whether it has silent-install flags like various flavours of Windows installer packages do. I iterated through the list at http://unattended.sourceforge.net/installers.php but had no success. I tried:

Code: Select all

PS C:\users> .\ce-launcher.exe /? PS C:\users> .\ce-launcher.exe /quiet /passive PS C:\users> .\ce-launcher.exe /quiet /passive PS C:\users> .\ce-launcher.exe /silent PS C:\users> .\ce-launcher.exe /S PS C:\users> .\ce-launcher.exe -s PS C:\users> .\ce-launcher.exe /s PS C:\users> .\ce-launcher.exe /s /v"/qb" PS C:\users> .\ce-launcher.exe /s /a /s /v"/qb"
I had a look at chocolatey.org and found https://chocolatey.org/packages/cryenginesdk but that's several years out of date. It looks like at the time the engine was distributed inside a zip.

I'd very much like to automate this part of the process to eliminate the chance of manual errors poisoning our build environment. Anyone able to assist?

Who is online

Users browsing this forum: No registered users and 3 guests