Introducing Orchestator Long Term Support (LTS) Version #810
Description
Orchestrator: Long Term Support (LTS) Version
- "The Endgame Version" - Complete Backlog
Orchestrator (formerly Cloud Runner) has reached minimum LTS readiness with what has been merged already. A final set of improvements is ready in PR to complete the remaining polish and bring the project fully to LTS readiness.
This milestone is not the same as 1.0.0.
1.0.0 meant the system was stable, production-ready, and validated through real-world usage. The architecture worked and the provider model proved itself.
LTS sets a higher bar.
LTS means the system now feels complete:
- the architecture has proven itself in real usage
- rough edges discovered during the 1.x cycle have been addressed
- convenience and operational workflows are in place
- the reasonable expansions of the system have been implemented
In other words, Orchestrator now covers its domain cleanly and confidently.
I've also been using orchestrator in professional + production and personal + production projects regularly in my own workflows, which has helped flush out the remaining gaps and polish the ergonomics around real CI usage.
We're now past the point where obvious new capabilities belong inside the core. Even for advanced enterprise workflows, the necessary primitives are already there. Future ideas are more likely to live around the ecosystem or as separate tools, rather than expanding the orchestrator core itself.
Another important piece reaching readiness alongside this milestone is the Unity Editor tooling.
A new editor package (game-ci-editor-tools) provides a GUI inside Unity for very easy setup of template workflows for Game-Ci instantly for any project or experience level, configuring workflows, triggering builds, downloading artifacts, inspecting caches, and viewing CI status, allowing teams to use Game CI conveniently by quickly installing template workflows to their repo and configuring workflows as needed without even needing to work directly with YAML.
From here the expectation is that the project requires much less active maintenance, because the infrastructure and convenience features needed for real-world use are already built in.
Future changes should mostly consist of:
- bug fixes
- experimental features graduating to stable
- ecosystem tooling around the core
Think of it as Orchestrator v2.0.0 — the mature successor to Cloud Runner.
There are two groups of work currently in PR before the LTS cut.
Thank you to everyone who has reviewed so far — I'll ask for your patience for one last wave. Full details in the thread.
Sub-Tracking Issues
This is the top-level overview for the Orchestrator LTS effort. All detailed tracking is in the sub-issues below:
Core Deliverables
| Issue | Title | Description |
|---|---|---|
| #794 | Orchestrator LTS (v2.0.0) | LTS release tracking — all core infrastructure PRs, enterprise features, build reliability, secret management, provider enhancements, documentation, merge queue, and release criteria. Start here for the full PR list and merge order. |
| #795 | Orchestrator LTS Next-Gen | Experimental features — Test Workflow Engine, Hot Runner Protocol, Generic Artifacts, Incremental Sync, Community Plugin Validation, Unity Editor Tooling, CLI support, and more. Built on the LTS foundation. |
Companion Projects
| Issue | Title | Description |
|---|---|---|
| #811 | Help Bot | AI-powered community support — Discord and GitHub help bot with context-aware responses. Separate repo: game-ci/help-bot. |
| #801 | Claude for Unity-Builder | AI-assisted development — CLAUDE.md, agent definitions, and skills for the unity-builder codebase. |
Complete Hierarchy
#810 (Orchestrator: The Endgame — top-level overview) <-- you are here
│
├── #794 (LTS v2.0.0) — Core LTS release
│ ├── PR #777 — Enterprise features (CLI providers, caching, LFS, hooks, submodule profiles)
│ ├── PR #778 — GCP Cloud Run + Azure ACI providers
│ ├── PR #783 — Provider load balancing
│ ├── PR #784 — Unit test coverage
│ ├── PR #786 — Secure git token handling
│ ├── PR #787 — Premade secret sources
│ ├── PR #806 — CI platform providers (PowerShell, GitHub Actions, GitLab CI, Ansible)
│ ├── PR #808 — Build reliability
│ ├── #776 (Premade secret sources — issue)
│ ├── #785 (Secure git token — issue)
│ ├── #805 (CI dispatch providers — issue)
│ ├── #807 (Build reliability — issue)
│ │
│ └── #795 (Next-Gen Final Features) — Experimental features
│ ├── #788 (Test Workflow Engine) → PR #790
│ ├── #789 (Hot Runner Protocol) → PR #791
│ ├── #792 (Generic Artifact System) → PR #798
│ ├── #793 (Incremental Sync Protocol) → PR #799
│ ├── #796 (Orchestrator Isolation) — future
│ ├── #797 (Unity Editor Tooling) → game-ci/game-ci-editor-tools
│ ├── #800 (Community Plugin Validation) → PR #804
│ ├── #802 (docs: massive projects) → docs PR #538
│ ├── #803 (docs: monorepo support) → docs PR #538
│ └── #812 (CLI support) → PR #813
│
├── #811 (Help Bot) → game-ci/help-bot
│
└── #801 (Claude for Unity-Builder) — AI assistance
All PRs Across All Repositories
game-ci/unity-builder
| PR | Title | Group | Status |
|---|---|---|---|
| #777 | Enterprise features — CLI providers, caching, LFS, hooks | LTS Core | Draft — 130+ tests |
| #778 | GCP Cloud Run + Azure ACI providers | LTS Core | Draft |
| #783 | Provider load balancing | LTS Core | Draft — 11 tests |
| #784 | Unit test coverage | LTS Core | Ready — 65 tests |
| #786 | Secure git token handling | LTS Core | Ready — 12 tests |
| #787 | Premade secret sources | LTS Core | Ready — 34 tests |
| #790 | Test workflow engine | Next-Gen | Draft — 43 tests |
| #791 | Hot runner protocol | Next-Gen | Draft — 35 tests |
| #798 | Generic artifact system | Next-Gen | Draft — 36+ tests |
| #799 | Incremental sync protocol | Next-Gen | Draft — 42 tests |
| #804 | Community plugin validation | Next-Gen | Draft |
| #806 | CI platform providers | LTS Core | Draft — 91 tests |
| #808 | Build reliability | LTS Core | Draft — 5 tests |
| #809 | CI integrity speedup | CI | Draft |
| #813 | CLI support | Next-Gen | Draft |
Total new tests: 504+ (348 LTS + 156 Next-Gen)
game-ci/documentation
| PR | Title | Status |
|---|---|---|
| #532 | Core orchestrator docs | Ready |
| #533 | Cloud provider guides | Draft |
| #535 | Build services reference | Draft |
| #536 | Load balancing API | Draft |
| #537 | Secret sources | Draft |
| #538 | Next-gen features + advanced topics | Draft |
| #540 | CLI documentation | Draft |
| #539 | Typo/formatting fixes | Ready |
game-ci/game-ci-editor-tools
| Item | Description | Status |
|---|---|---|
| Main branch | 6 editor tools (3 stable + 3 experimental) | Implemented |
| PR #1 | Hot runner worker — 5 transports | Complete |
game-ci/help-bot
| Item | Description | Status |
|---|---|---|
| Repository | Discord + GitHub help bot with AI responses | Implemented |
By the Numbers
| Metric | Count |
|---|---|
| New PRs (unity-builder) | 15 |
| New PRs (documentation) | 7 |
| New issues | 20+ |
| New repositories | 2 (help-bot, game-ci-editor-tools) |
| New action inputs | 63 (LTS) + 24 (Next-Gen) = 87 |
| New services | 8 (LTS) + 8 (Next-Gen) = 16 |
| New tests | 504+ |
| New C# files (editor tools) | 13+ |
Quick Start for Reviewers
Copy the prompt below into Claude or Codex anywhere to explore the full scope of changes interactively.
Please query the recent github issues in game-ci/unity-builder
We will referer to this group of changes as "orchestrator LTS version". This includes "next-gen" and LTS (v2.0.0) issues.
Created by user frostebite. Entrypoints are: https://github.com/game-ci/unity-builder/issues/810, https://github.com/game-ci/unity-builder/issues/811
Help me evaluate all of the changes. In a prioritized step by step manner. Assuming we are open-source maintainers of these tools and these changes have been recently submitted by our co-contributor frostebite/fish. You will offer various options to interact with these issues and PRs appropriate for open source contributors first receiving these submissions and information.
Help me formulate any kind of response I feel like, in no rush and obligation.
Fish does have the practical challenge he MUST GET review approvals one by one on each PR.
Recommended to use AI to help review and approve.
New repositories:
- game-ci/help-bot
- game-ci/game-ci-editor-tools
Changes to existing repository:
- game-ci/unity-builder
clone this repos or prompt the user to tell us if they already exist and we should use those folders. we will have to switch branch so make sure there are no working changes. prompt the user if we will need to wipe local changes.
Give me a simple overview of the changes being proposed. Give me some quick options I might want to perform as a contributor considering there are new issues, PRs and repositories to explore and review. Particularly suggest actions like:
- jumping in with the repo to test it locally,
- analyze the quality of changes such as consistency/adherence to standards and patterns/technical correctness,
- talk more about the architecture and conceptual changes,
- provide requested PR reviews,
- assess risk and change to existing functionality vs functionality added separate or isolated from existing functionality.
- fast review and approval on anything that needs it.
All of the involved changes are referenced within refrences that can be found exploring from those issues, expand out to find them.
Integration PRs
These combined PRs merge all individual feature PRs into single reviewable branches:
| PR | Branch | Scope | Component PRs |
|---|---|---|---|
| #815 | release/lts-2.0.0 |
All 15 PRs (infrastructure + next-gen) | #777, #778, #783, #784, #786, #787, #806, #808, #809, #790, #791, #798, #799, #804, #813 |
| #816 | release/lts-infrastructure |
9 infrastructure PRs only | #777, #778, #783, #784, #786, #787, #806, #808, #809 |
| #814 | release/next-gen |
6 next-gen feature PRs | #790, #791, #798, #799, #804, #813 |
Each integration branch includes delete-me-update-this-integration-branch.ps1 and delete-me-update-all-integration-branches.ps1 scripts to keep them in sync with component branches.