Builds & release
Builds
Section titled “Builds”Builds live in Tasks → Automations → Builds. On top are the two downloads most people come for: the newest development build and the newest release, one press each, for everyone in the studio, CI login or not. Below, each pipeline is a row of its recent runs; a run opens with its steps, times, log, artifacts and commit. Run (with its parameters), Cancel and Pause reach the computer that runs the build, so they work from anywhere, the phone included.
A build computer in one click
Section titled “A build computer in one click”Any studio computer becomes a build computer for the project’s engine:
| Engine | Its build |
|---|---|
| Unreal | compile, test, package |
| Godot | export, with the project’s own preset |
| Unity | build the player from Build Settings |
| Your own | whatever its connector ships |
Set it up from the button on the Builds page: this computer, this project, its version control (found for you), the branch, a preset, Start. No computer becomes a build computer until someone asks it to, and a build step runs only the commands its engine’s connector ships, never a command typed into an automation.
TeamCity and Horde
Section titled “TeamCity and Horde”Connect a TeamCity or Horde server and its pipelines show beside kumo’s own, read and driven through its API. Only its newest development and release builds are copied to the studio for download.
Publishing to the stores
Section titled “Publishing to the stores”Publish to a store is a build step, usually right after packaging:
| Store | What runs | Where it goes |
|---|---|---|
| Steam | SteamCMD | a beta branch, set live if you say so |
| Epic Games Store | BuildPatchTool | a label |
| GOG | GALAXY Pipeline Builder | a branch |
| itch.io | butler | a channel |
| Microsoft Store | Partner Center | a flight or the public submission |
| Meta Quest | ovr-platform-util | a release channel |
| App Store | Xcode’s uploader, on a Mac | TestFlight; a person releases it |
| Google Play | the Publishing API | a track, with a rollout share |
| PlayStation, Xbox, Switch | your own script around the platform’s licensed tools | the platform’s own process |
The step uses the build computer’s own connection to each store, set up by whoever runs that computer; no studio secret is handed to it.
Products, demos and releases
Section titled “Products, demos and releases”A product is the game, a DLC, a demo, a soundtrack or a bundle, each keeping its store text and pictures once in Tasks → Production → Products. kumo sends it to App Store Connect and Google Play through their APIs, and gives you a checklist to copy it to Steam, Epic, GOG and the rest. A demo is a product of its own, with its own build, store page, release row and end date, and its owners are told before it ends. See Products and store pages.
Each build that reaches a store is a row under Releases: what shipped, where and when.
Localization
Section titled “Localization”Tasks → Production → Localization reads the game’s own localization files: a translation memory built from them suggests and checks translations, and the glossary is a sheet in the wiki.
Strings with Crowdin or Lokalise
Section titled “Strings with Crowdin or Lokalise”When the progress is read from Crowdin or Lokalise and the Unreal project is on this computer, Localization also syncs the game’s strings:
- In Unreal, export the target’s text (the Localization Dashboard’s
Export Text). Each culture gets its
.pofile. - Click Send the strings. The native culture’s file goes up as the source.
- When translators are done, click Get the translations. Each culture’s translated file comes down over its own. Both does the two in turn.
- In Unreal, import the text (Import Text) and compile it.
kumo says which cultures it wrote, which were already up to date, and which
the tool does not translate. In an automation, after the export step, run
kumo integrations run --only crowdin -- py -m planner loc sync --root <project>
(or --only lokalise).