Command Line
You can run orchestrator builds directly from your terminal - no GitHub Actions or CI platform required. All parameters in the API Reference can be specified as CLI flags.
Install
Linux / macOS
curl -fsSL https://raw.githubusercontent.com/game-ci/orchestrator/main/install.sh | sh
Windows (PowerShell)
irm https://raw.githubusercontent.com/game-ci/orchestrator/main/install.ps1 | iex
Pre-built binaries for every platform are available on the GitHub Releases page.
Examples
Local build
game-ci build \
--target-platform StandaloneLinux64
Cloud build (AWS)
game-ci build \
--target-platform StandaloneLinux64 \
--provider-strategy aws \
--git-private-token $GIT_TOKEN
Cloud build (Kubernetes)
game-ci build \
--target-platform StandaloneLinux64 \
--provider-strategy k8s \
--git-private-token $GIT_TOKEN
List active resources
game-ci list-resources --provider-strategy aws
Watch a running build
game-ci watch --provider-strategy aws
Clean up old resources
game-ci garbage-collect --provider-strategy aws
Cleans up stale cloud resources (AWS only): stops old ECS tasks, deletes job CloudFormation stacks,
and removes old CloudWatch log groups. Resources are deleted immediately without confirmation. Use
--garbageMaxAge to control the age threshold (default: 24 hours).
Keeping Commands Short
Avoid long CLI flags for credentials by using environment variables or the Pull Secrets feature:
game-ci build \
--target-platform StandaloneLinux64 \
--populate-override true \
--pull-input-list UNITY_EMAIL,UNITY_SERIAL,UNITY_PASSWORD \
--input-pull-command='gcloud secrets versions access 1 --secret="{0}"'
Further Reading
- CLI Getting Started - installation options, license activation, first build walkthrough
- Build Command Reference - full list of build flags
- Orchestrate Command - cloud-specific options
- Other Commands - license activation, cache management, and more