Game Development Reference
In-Depth Information
4
Continuous Integration for Games
Steven Ramirez
4.1 Introduction
Video games are made up of complex systems that form a cohesive, high-performance
application. Content creation for those systems involves using external tools, such
as Maya and Photoshop, to take an asset from concept to running in-engine. De-
velopers establish asset pipelines to streamline that process. While each team has
their own demands that need to be met, there are requirements that overlap for all
teams. This can include automation of unit/build testing, asset generation, build
creation, and notification of build errors. CruiseControl.NET (CCNet) is a free,
open-source suite of applications by ThoughtWorks that provides the functionality
for the above tasks through XML configuration files and the integration server.
This chapter explaains how to use the CruiseControl.NET server and provides a
framework for you to use.
4.2 Build Pipelines: How Do They Work?
The process of taking source code and assets from their original format to the
final, playable game format is called the build pipeline. Build pipelines can provide
you with essential information you need in real time. This information can be the
current state of the build, unit test failures, and asset changes. Here, we will discuss
parts of the build pipeline.
4.2.1 What is CruiseControl.NET?
CCNet is a suite of applications created for the purpose of managing and automat-
ing the build pipeline. There are three parts to CCNet: the automated integration
server, a web interface called the Web Dashboard and the notification tool called
CCTray.
39
