Builds

Doing rather than reading?

Make a Build walks it in order.

Builds are configured and executed from unity by one of the people working in Unity and uploaded to our internal launcher for the testers.

We will soon create an external build tool that uses Unity CLI to create builds without using the editor directly.

Versioning

Builds are named [Game]_[Major].[Minor].[Patch]_[BuildNumber], for example TorturedHome_0.4.2_318.

The build number increments on every build and is the thing testers quote in a bug report, so it has to be visible in-game. The version itself lives in Unity's Player Settings and is bumped deliberately, not per build.

What gets built

Every build comes from main (see Version Control > Branching), includes all scenes in the build list, and is a development build with the profiler enabled, unless it is a release candidate.

Platform for internal testing is Windows x64.

Changelog

Changelogs are generated from the commit messages since the last labelled build, grouped by commit type:

  • feat and fix are shown to testers.
  • chore, refactor, docs, style, test, build and ci are hidden.

This is the reason the commit format matters. Nothing else has to be written for a changelog to exist. The data is already in the history, in the right shape.