In our case, we compared Bamboo, Jenkins and TeamCity and finally decided on TeamCity due to its flexibility and ease of use, but pretty much any CI server should work great depending on the feature set that you need. CI servers are excellent for this, even if you don’t want to use anything CI specific.

Three major pieces of the puzzle were:īuild server is the heart and soul of the system, since it monitors source control (git in our case), coordinates between multiple build agents and executes builds. This is why we decided to build our own infrastructure, in-house. As an example, Top Eleven has a lot of auto-generated code that requires starting Unity four times in a row for all of it to compile properly, while another project uses 2 different source control systems at the same time.

The biggest problems were our code repositories not being exposed to the internet, and complex build pipelines that we need to be in full control of. A really good solution is Unity Cloud Build, but most of our games don’t fit the imposed limitations. And since it only takes one push to the source code repository to get the latest version to run on your device, our artists and game designers became much more involved with the faster iterations on the project.Īutomated builds and continuous integration (CI) solutions have been widely researched and implemented, but there is very little information that is specific to Unity.

This is one of the main reasons we wanted to automate our builds and offload them from the developer machines into the cloud. In one of our projects, developers were waiting for upwards of 15 minutes to get the Android version of the game. Building any large Unity project can take a lot of time while preventing you from using the editor during the process.

Unity cloud build sloqw