Game dev is a laborious process. Creating code and art assets is time-consuming enough but it’s easy to get bogged down in repetitive tasks like making builds, packaging and uploading copies of the game for testing, and baking lighting.

In this talk we will explore how to automate different parts of a typical Unity workflow using Jenkins. Building our continuous integration workflow, we will also aim to reduce the chance for mistakes to slip into the process and ensure that all builds are reproducible.

Topics for talk

• Why Jenkins? Comparing a custom solution using Jenkins to Unity Cloud Build
• Using Jenkins to manage creating builds
• Pre-build tasks: Including git revision info in build
• Post-build tasks: Package build in installer
• Automating other tasks
  -Running unit tests
  -Bake lighting and commit back to project

===

Rory Dungan has been working with Unity for over four years. Currently he uses it every day at District Technologies, a brand new health and fitness app that turns your city into an urban exploration game. In the past, Rory has also used Unity to work on projects ranging from VR experiences on the Rift, Vive, Gear and Oculus Go to tablet apps and engineering visualisation tools. In his spare time he sometimes works on game projects and currently maintains a couple of open-source editor extensions and libraries.