Skip to content
kumo

Builds & release

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.

Any studio computer becomes a build computer for the project’s engine:

EngineIts build
Unrealcompile, test, package
Godotexport, with the project’s own preset
Unitybuild the player from Build Settings
Your ownwhatever 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.

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.

Publish to a store is a build step, usually right after packaging:

StoreWhat runsWhere it goes
SteamSteamCMDa beta branch, set live if you say so
Epic Games StoreBuildPatchToola label
GOGGALAXY Pipeline Buildera branch
itch.iobutlera channel
Microsoft StorePartner Centera flight or the public submission
Meta Questovr-platform-utila release channel
App StoreXcode’s uploader, on a MacTestFlight; a person releases it
Google Playthe Publishing APIa track, with a rollout share
PlayStation, Xbox, Switchyour own script around the platform’s licensed toolsthe 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.

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.

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.

When the progress is read from Crowdin or Lokalise and the Unreal project is on this computer, Localization also syncs the game’s strings:

  1. In Unreal, export the target’s text (the Localization Dashboard’s Export Text). Each culture gets its .po file.
  2. Click Send the strings. The native culture’s file goes up as the source.
  3. When translators are done, click Get the translations. Each culture’s translated file comes down over its own. Both does the two in turn.
  4. 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).