Skip to main content
Version: v4 (current)

Standalone Orchestrator CLI

The standalone Orchestrator CLI is an advanced entry point for running Orchestrator directly. It is useful for provider development, debugging, and environments that need the orchestration backend without installing the public game-ci CLI.

Most users should use the public GameCI CLI. The public CLI exposes the higher-level user API and can load Orchestrator as a provider plugin.

When To Use It​

Use caseEntry point
General local or CI commandsGameCI CLI
Remote jobs through a friendly CLIgame-ci remote run with the Orchestrator plugin
GitHub Actions Unity buildsgame-ci/unity-builder@v4
Provider protocol development or debuggingStandalone Orchestrator CLI

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 are available on the Orchestrator releases page.

Example​

game-ci build \
  --target-platform StandaloneLinux64 \
  --provider-strategy aws

This command talks directly to the Orchestrator package. The public CLI equivalent is:

game-ci \
  --plugin @game-ci/orchestrator-plugin \
  remote run ./my-project \
  --provider-strategy aws \
  --target-platform StandaloneLinux64

Relationship To Unity Builder​

When you use game-ci/unity-builder@v4 with providerStrategy, unity-builder loads Orchestrator as an optional plugin. You do not need to install the standalone Orchestrator CLI in that path.

- uses: game-ci/unity-builder@v4
  with:
    providerStrategy: aws
    targetPlatform: StandaloneLinux64

Next Steps​